Release Notes for Cisco IOS Release 15.5(2)T
New Features in Cisco IOS Release 15.5(2)T
Determining the Software Version
Upgrading to a New Software Release
Erasing the Configuration File
Virtual WPAN (VWPAN) Interface
Interface Configuration and Monitoring
Obtaining Documentation and Submitting a Service Request
First Published: March 30, 2015
These release notes contain the latest information about using Cisco IOS software with the
Cisco 1000 Series Connected Grid Routers (CGR 1000 or routers) for Release 15.5(2)T.
This release includes support for the Cisco 500 Series WPAN Industrial Routers (IR500). The IR500 series includes:
■IR509 WPAN Gateway, a distribution automation (DA) gateway that provides secure IPv4/IPv6 connectivity over IPv6-based CG-Mesh to DA devices such as capacitor bank controllers, reclosers, or other SCADA devices.
■IR529 WPAN Range Extenders (Basic and Advanced) extend the range of an RF wireless mesh network, providing longer reach between WPAN endpoints and other WPAN networks. WPAN range extenders support the full CG-Mesh network platform, including IEEE 802.15.4g/e, IEEE 802.1X, IPv6, and RPL.
IR500 series operate with the CGR 1000 and Cisco Connected Grid Network Management (CG-NMS) as part of the Field Area Network (FAN) solution.
This release also adds support for the Cisco 819 Integrated Services Router (ISR). The 819 ISR supports 3G, 4G, and 3G with dual radio 802.11n Wi-Fi form factors combined with full features of Cisco IOS Software. The Cisco 819 ISR combines the latest cellular standards (4G LTE), 3G standards (High-Speed Packet Access Plus [HSPA+] release 7 and Evolution Data Optimized [EVDO] Rev A) with Cisco enterprise-class wireless LAN solutions into a single platform.
For more information about the IR500 series and the other FAN components, refer to the documents listed in Related Documentation.
You can download the software from this site (registered Cisco.com users with a login password):
http://software.cisco.com/download/navigator.html
This document uses the following conventions.
Note: Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.
Caution: Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data.
Warning: IMPORTANT SAFETY INSTRUCTIONS
Means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.
SAVE THESE INSTRUCTIONS
Regulatory: Provided for additional information and to comply with regulatory and customer requirements.
New Feature Summary for Cisco IOS Release 15.5(2)T lists the new features added in Cisco IOS Release 15.5(2)T.
The IR500 series connects to DA devices using serial ports (RS232/RS485) and/or an Ethernet port using IPv4. The IR500 series provides remote connectivity to serial DA devices over CG-Mesh by transporting serial data over TCP/IP. The IR500 series also provides remote connectivity to IPv4 DA devices over the IPv6-based CG-Mesh by using Mapping of Address and Port using Translation (MAP-T). The IR500 series performs NAT44 translation to translate private IPv4 addresses used by DA devices connected to the Ethernet port to public IPv4 addresses used with MAP-T.
|
■ Cisco IR 500 Series WPAN Gateway and Range Extender Installation and Configuration Guide |
|
The 4.1 release of Device Manager adds support for the IR500 series WPAN, in addition to support for the CGR 1000 running Cisco IOS.
Device Manager connects to the IR500 directly over the laptop COM port, either with or without a work order. Device Manager displays IR500 hardware status and allows you to configure and view settings for MAP-T, TCP raw socket, WPAN, RPL, and other protocols used by the IR500 in the CG-Mesh network.
|
■ Connected Grid Device Manager 4.0 and 4.1 (Cisco IOS) Release Notes ■ Cisco Connected Grid Device Manager Installation and User Guide (Cisco IOS), Release 4.0 and 4.1 |
|
■ Release Notes for Cisco Connected Grid Network Management System, Release 2.1.1 ■ Cisco Connected Grid Network Management System User Guide, Release 2.1.1 |
||
Refer to
Documentation Updates.
|
||
■ Industrial Operations Kit Getting Started Guide |
||
The Cisco 819 Integrated Services Router Family, designed in compact hardened and non-hardened form factors, is the smallest Cisco IOS Software router with support for integrated fourth-generation (4G LTE) wireless WAN (mobile broadband backhaul) capabilities. The Cisco 819 ISR gateway provides a rapidly deployable, highly available, reliable, and secure solution designed specifically for machine-to-machine (M2M) applications.
|
||
Refer to
Documentation Updates.
|
||
Refer to
Documentation Updates.
|
||
Minimum Software Requirements lists the software versions associated with this release for Cisco products deployed in a FAN solution.
This section includes the following topics:
■Determining the Software Version
■Upgrading to a New Software Release
■Erasing the Configuration File
To identify the software version operating on the Cisco IOS router, enter the following command:
The software image is a bundle image and includes the following components: Cisco IOS image, Guest OS, Hypervisor, and a Virtual Device Server. When you initiate installation of the software, all of the components automatically install on virtual machines with the router.
To install a new version of software, you copy the bundle image over to flash and issue the bundle install command to upgrade the software.
You will then see output similar to the following:
After the software installation bundle finishes and displays Done! on the screen, enter the following commands to save the configuration and complete the installation process on the router:
When you enter the write erase { /all nvram: } /no-squeeze-reserve-space file-system : | file-system : | startup-config command, it erases a specified item or initiates an action to save memory on the Cisco 1000 Series router. See specifics in write erase command.
Cisco recommends that you review this section before you begin working with the router. These are known limitations that will not be fixed, and there is not always a workaround for these issues. Some features might not work as documented, and some features might be affected by recent changes to the CGR 1000 router hardware or software.
Hardware Limitations lists the limitations in this release for hardware features that are described in detail in the
Cisco Connected Grid Router Hardware Installation Guide for the Cisco CGR 1120 or CGR 1240.
|
Symptom On the CGR, "%Please shutdown the interface before removing it" displays when you configure the dialer as a default interface.
Conditions Dialer is already in a shutdown state, and the console displays "%Please shutdown the interface before removing it". Dialer is configured as a default interface.
Workaround Remove Dialer Pool and then the default interface dialer 1 command executes with no errors.
Minimal Support for SNMP write on ciscoWan3gMib for Security Reasons
The read-write operation only permits the following OIDS in CISCO-WAN-3G-MIB.
Note: See related ciscoWan3gMib caveats in this section CSCuh85612, CSCuh88771, CSCuh88904, CSCuh88968, CSCui00861, CSCui01208, CSCui01347, CSCui03505
Symptom A write on c3gGsmRoamingPreference results in commit failed."
SNMP write on most of ciscoWan3gMib is not supported for security reasons.
Conditions When you issue snmp set on c3gGsmRoamingPreference, you get the error message “Commit failed.”
Workaround There is no workaround. Limitation is by design for security reasons.
Symptom c3gMsisdn shows an empty string in an SNMP walk.
Conditions SNMPget on c3gMsisdn.
Workaround There is no workaround. This issue is carrier dependent. When this issue is seen in the field, check with your service provider to see whether MsIsdn is populated by the service provider. For example, AT&T does provide the MsIsdn value and T-Mobile does not.
Symptom When a SNMP set is issued to create a row in the PDP profile table, commitFailed was seen.
Conditions SNMP set operations are not allowed on c3gGsmPdpProfileTable for security reasons.
Workaround Use the CLI to create a new profile for profile 3 as shown in the example below:
Symptom ciscoWan3Gmib does not support a write function for the c3gGsmChv1 object.
Conditions When a user issues a set c3gGsmChv1 command, the set fails. By design, the write function (disabled by default) does not work on most of the ciscoWan3gMib for security reasons.
Workaround Enter the command cellular slot/port gsm sim change-pin Old-PIN New-PIN to set Card Holder Verification 1 (CHV1). Example below:
Symptom A write on c3gCdmaSecurityTable results in commit failed.
Conditions User uses snmp create a row in the security table as the MIB has access to create a row. This results is failure as write is not supported in IOS for this MIB.
Workaround There is no workaround for this issue. SNMP write on most of ciscoWan3gMib is not supported for security reasons.
Either objects are pre-set or can be set through CLI. SNMP set is not supported.
Symptom The OID c3gHdrDdtmPreference is not writable even though it is a read-write object. SNMP write on c3gHdrDdtmPreference is not supported for security reasons.
Conditions The requested set on c3gHdrDdtmPreference always results in Commit Failed errors.
Workaround Enter the [ no ] cdma ddtm command to set the c3gHdrDdtmPreference for a cellular preference as enabled or disabled. For example:
To enable cdma ddtm for cellular 3/1:
Symptom MIB OID c3gCdmaRoamingPreference does not have corresponding CLI. The write operation of c3gCdmaRoamingPreference results in "Commit failed" errors. The write of c3gCdmaRoamingPreference is not supported due to security reasons.
Conditions User wants to identify the Roaming Preference through CLI. its not shown. It is available only via mib get.
The write of c3gCdmaRoamingPreference results in "Commit failed" errors.
Workaround Use c3gCdmaRoamingPreference get to retrieve the Roaming Preference value.
Symptom Issue snmpset on any of c3gMdn,c3gCurrentNid, c3gCurrentSid,c3gSipUsername or c3gSipPassword MIB objects. The following occurs:
Conditions SNMP write on most of the ciscoWan3gMib is not supported for security reasons.
Workaround There is no workaround.
Symptom Cannot SSH into the CGR with SSHv2 protocol.
Conditions SSH process is operating in its default configuration. That is, it is neither configured with ip ssh version X nor is it configured with ip ssh version 2.
In addition, the SSH process is not configured with ip ssh rsa keypair-name XXXX to specify a SSH host key.
Subsequently, SSH process uses the SUDI RSA key as SSH host key.
User should manually create a new SSH host key by following these steps:
1) To generate a new key, enter command crypto key generate rsa modulus 2048 label XXXX in configuration (config) command mode.
2) To specify the use of key XXXX as SSH host key, enter command ip ssh rsa keypair-name XXXX in config command mode.
3) To specify the use of the SSHv2 protocol, enter command ip ssh version 2 in config command mode.
Symptom When using Airspan base station with CGR1000 dot16 modules, the latency may increase if the dot16 uplink throughput is very low (around 200 Kbps or less).
Conditions If the uplink throughput is very low (around 200 Kbps or less), the latency may increase (especially with the Best Effort service-class). This is because Airspan base stations expect a certain minimum rate of traffic before processing the traffic.
Workaround Configure a QoS scheduling method like rTPS on the base station to minimize the increase in the uplink latency at very low traffic rates.
Symptom You cannot download the software image bundle for this release when operating with SSHv1.
Conditions By default, the GOS image that comes with the software bundle image only supports SSHv2. You must enable SSHv2 in Cisco IOS in order to download any TPMC package or application to the GOS.
Workaround Enable SSH2 in Cisco IOS.
Symptom The system reset-reason may show “Thermal Trip” after a power outage.
Conditions When a CGR is power-cycled due a power loss event, the system reset-reason may show a false “Thermal Trip” reset instead of “Power-on”. This is because the unstable voltage on the mainboard may trigger a false “Thermal Trip” reset-reason.
Workaround After the CGR comes back up, issue show environment temperature to check the sensor temperature. If they show normal values, the Thermal Trip reset-reason can be ignored and no further action needs to be taken.
Symptom The line protocol on the dot16 interface may not go down after restoring the interface to default configuration.
Conditions Configure the necessary settings for the dot16 interface to come online. Restore the interface to default settings. The dot16 interface line protocol may stay up.
This section addresses the open caveats in this release and provides information on how to use the Bug Search Tool to find further details on those caveats. This section includes the following topics:
Symptom The message, modem is not present, is seen when the modem is plugged in.
Conditions Module is stressed with power UP/DOWN, dual SIM failovers, and modem power cycles and resets along with traffic.
Workaround There is no workaround for this issue. Reboot the CGR.
Symptom Modem crash memdump from the modem is not retrieved.
Conditions Even when the modem crash tool is enabled, the memdump is not retrieved.
Workaround There is no workaround for this issue.
Symptom The AT Command response from the modem is very slow when bidirectional traffic is sent across the cellular interface.
Conditions Bidirectional traffic is sent across the cellular interface.
Workaround Stop all traffic and reload the CGR to access the AT commands.
Symptom The following tracebacks are seen when GSM/CDMA modem crashes:
%SYS-3-BAD_RESET: Questionable reset of process 314 on tty3/1
-Process= "TTY Daemon", ipl= 0, pid= 333
-Traceback= 1845341z 1733927z 1734FA8z 22D2AA0z
Conditions Occurs when CDMA/GSM modem crashes.
Workaround Perform module reload by entering the command: hw-module reload slot-number.
Symptom After booting, a cellular interface might not automatically be placed in an admin non-shut state when its 3G module is administratively powered up from a powered-down state.
Conditions When the 3G module is powered down, its cellular interface will also be put in admin shut state. When the 3G module is powered up again, its 3G interface will be automatically put back in admin no-shut state.
However, if the 3G module is powered-down and the CGR is rebooted, the 3G interface may not be put in admin no-shut state when the 3G module is powered up again. Users may see this error "cellular_error_log: DS instance init issue". When such an error occurs, the cellular interface will not be automatically put in admin no-shut state when the 3G module is powered up.
Workaround Try to manually bring up the cellular interface by using the no shutdown command
Symptom Cellular 3G interface is shown in shutdown state even after the module is powered on.
Conditions CGR (with a 3G module installed) was powered off and reloaded to ensure that the cellular interface was not in an admin down state. After the CGR boots up and the 3G module is powered on, the module remained in an admin down state.
Workaround Shutdown and no shutdown commands need to be performed on the cellular interface after the CGR boots up.
Symptom The dot16 interface may be set to admin shut in startup-config under some race conditions.
Conditions Under some race condition (e.g. a copy run start operation is happening during a module power-cycle due to recovery or wan-mon), the dot16 interface configuration may be set to administrative shutdown. If the CGR is reloaded, this interface may stay in admin shut state
Workaround Issue no shutdown in the interface configuration mode if the interface stays in the admin shut state after a reload.
Symptom c3gModemTemperAbateNotif trap generates only after the c3gModemTemperOnsetNotif trap has already been generated once.
Conditions c3gModemTemperAbateNotif is working like recovery trap rather than a discrete trap.
Workaround There is no workaround.
Symptom Malloclite memory leak occurs every 15-20 minutes.
Conditions This issue is reproducible, but not consistently. An example is shown below:
Workaround There is no workaround. Router reboot does not help.
You can use the Bug Search Tool to find information about caveats for this release, including a description of the problems and available workarounds. The Bug Search Tool lists both open and resolved caveats.
To access Bug Search Tool, you need the following items:
■Cisco.com user ID and password
To access the Bug Search Tool, enter the following URL:
https://tools.cisco.com/bugsearch/search
To access the Bug Search Tool to search on a specific caveat, enter the following URL:
This section includes the following late updates to documentation for the CGR 1000:
■Virtual WPAN (VWPAN) Interface
■NTP timing based on GPS Clock
The CGR 1000 provides security services to wireless and power-line communication (PLC) mesh endpoints. This is done by enabling these services on corresponding WPAN and PLC IOS interfaces. For a partner-developed WPAN module that connects to Guest-OS (GOS), the same set of services are not directly available.
A new Virtual WPAN interface is included in this Cisco IOS release to provide 802.1X and Mesh-security services. This interface serves as the anchor to the Port Access Entity (PAE) for the partner module and the end-points. It also provides configuration and monitoring CLI commands.
The VWPAN interface has three main subsystems:
■Partner Module - The module connects to GOS directly using USB. The partner module must have an embedded 802.1X supplicant.
■Extensible Authentication Protocol ( EAP) relay application - A partner-developed GOS application that functions as an EAP relay between the module and IOS. EAP packets received from the module are forwarded to Cisco IOS and are likewise processed in the reverse direction. The application uses an API library (libvwpan) that Cisco provides to communicate with Cisco IOS.
■Cisco IOS Virtual WPAN interface - Provides the 802.1X and Mesh-security services for partner module and mesh endpoints.
Figure 1 shows the high-level architecture.
VWPAN 1X and Mesh-security interface configuration and monitoring is identical to the physical WPAN interface. All the 802.1X and Mesh-security CLI commands are available and behave the same way.
For example, the following creates and configures a VWPAN interface and sets up the 802.1X authenticator in multi-auth mode:
To configure raw socket over MPLS VPN, enable encapsulation trans on the asynchronous interface, then use the xconnect command to configure the MPLS virtual connection.
When data comes in from the asynchronous mode serial port (or UART), the CGR 1000 packetizes the data using the configured criteria for raw socket and passes the packet to a pre-configured MPLS connection to another point. Then the packet is delivered to a local UART. This process is bidirectional.
The following example shows a serial interface on the CGR 1000 configured for Raw Socket MPLS VPN:
For more information about raw socket configuration on the CGR 1000, see Raw Socket Transport Software Configuration Guide for Cisco 1000 Series Connected Grid Routers (Cisco IOS).
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
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.
All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version should be referred to for latest version.
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices.
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)
No combinations are authorized or intended under this document.