Release Notes for Cisco Embedded Service 6300 Series Router - Release 17.5.1
Image Information and Supported Platforms
The following features are not supported on the ESR6300 with software release 17.5.1:
This release has the following limitations or deviations for expected behavior:
Alarm port Support on the ESR6300
Communications, Services, and Additional Information
The following release notes support the Cisco ESR6300 router. These release notes are updated to describe new features, limitations, troubleshooting, recommended configurations, caveats, and provide information on how to obtain support and documentation.
Cisco ESR 6300 SKUs provides the hardware product IDs and brief descriptions for the boards.
Embedded Router Board without a cooling plate. (NCP = No Cooling Plate) |
||
Embedded Router Board with cooling plate. (CON = Conduction cooled). |
This publication consists of the following sections:
■ Image Information and Supported Platforms
■ Caveats
The ESR6300 is a small form factor embedded router module with a board size of 3.0" x 3.775"(76.2mm x 95.885mm). The more compact design simplifies integration and offers system integrators the ability to use the Cisco ESR 6300 in a wide variety of embedded applications. The ESR card is available with a Cisco-designed cooling plate customized to the ESR, as well as without the cooling plate for system integrators who want to design their own custom thermal solution.
Note : You must have a Cisco.com account to download the software.
Cisco IOS-XE Release 17.5.1 includes the following Cisco image:
■c6300-universalk9.17.05.01.SPA.bin
The latest software downloads for the ESR6300 can be found at:
https://software.cisco.com/download/home/286323433
Click on the ESR6300 link to take you to the specific software you are looking for.
■No support for MacSec or DLEP in this release. (MQC: modular quality of service command line).
■Layer 2 COS to DSCP mapping does not work due to no ASIC chipset support for the feature.
■Copper FE SFPs are not supported on the ESR6300.
■Copper GE SFPs are only supported in config terminal > service internal > service unsupported-transceiver mode.
■Cisco does not claim IP Mobility for Ethernet support on the ESR6300.
■Auto-negotiation for 10Mbps, 100Mbps, 1000Mbps in full-duplex mode is supported. For half duplex, support is only on 10Mbps and 100Mbps.
■Refer to the Cisco Approved Vendor List (AVL]) for Cisco USBs. Kingston USB 3.0 works as well. Ensure the USB has a single partition and ext2, Fat16, or Fat32 format only.
■Cellular functionality is not supported.
■Radio Aware Routing is not supported.
■For Security: No support for TLS, TrustSec, MacSec, CWS [Cloud Web Security], IDS/IPS.
■The WebUI Licensing Page is unsupported for release 17.5.1. For all licensing configuration, please use CLI mode or CSSM.
■In the Web User Interface (WebUI), there are two known issues where erroneous information is displayed. In both of these cases, the information is present in the WebUI even though the functionality is NOT supported on the ESR6300.
–Under Configuration > Security > Threat Defense > snort there is a RAM and DISK size prerequisite check that fails.
–Under Configuration > Security > there is a category for Trustsec.
These are both cosmetic issues due to the features being unavailable in the 17.5.1 release.
■The IOS boot system setting allows users to specify any flash-based storage URL for IOS image booting.
The rommon on the ESR6300 does not expose the non-IOX msata partition, therefore auto-booting from mSATA will not work even if it is configured in IOS.
Example : Users must not configure a boot system setting as follows:
■Receive a message 'unable to open bootflash:golden.bin (14)' during bootup.
Example: Pushing the reset button displays the unable to open message.
This message is intended by design to inform the user they have not setup a golden.bin config file.
Note : Starting with Cisco IOS XE Amsterdam 17.3.2, with the introduction of Smart Licensing Using Policy, even if you configure a hostname for a product instance or device, only the Unique Device Identifier (UDI) is displayed. This change in the display can be observed in all licensing utilities and user interfaces where the hostname was displayed in earlier releases. It does not affect any licensing functionality. There is no workaround for this limitation.
The licensing utilities and user interfaces that are affected by this limitation include only the following: Cisco Smart Software Manager (CSSM), Cisco Smart License Utility (CSLU), and Smart Software Manager On-Prem (SSM On-Prem).
The following features are included in the Cisco IOS-XE release 17.5.1:
RFC 4884 redefines selected ICMP error messages to support multi-part operation.
A multi-part ICMP message carries all of the information that ICMP messages carried previously, as well as additional information that applications may require.
RFC 4884 feature introduces an 8-bit length attribute to the following ICMPv6 messages with extensions.
■Destination Unreachable (type = 1)
As part of RFC 4884 feature, for applications like MPLS/trace route which add extensions to type 1 and type 3 ICMPv6 error messages, original datagram length will be added in ICMPv6 header.
Also, infra is added as part of RFC 4884 support. If any new application is adding extensions it has to call defined registries to be compliant with RFC 4884.
Backward compatibility is also taken care of as part of this feature.
This feature is enabled by default and a CLI “[no] ipv6 icmp od-length enable” is provided which is enabled by default.
Note : RFC4884 ICMP v4 and MPLS v4 extensions will be supported in the IOS-XE 17.6.1 release.
The Netboot (TFTP boot) feature is now supported on the ESR6300. The ESR6300 has two Combo ports, Copper and Fiber ports (SFP) ports that support TFTP boot.
The Netboot (TFTP boot) feature allows the user to recover their router in the case that there is no image in the bootflash or USB.
The following configuration needs to be in place in ROMMON:
■WAN port Gigabit-Ethernet 0/0/0 or 0/0/1 should be connected to a TFTP network
■Path to image should be in a TFTP directory
■set IP_ADDRESS=<IP address of router>
There is one alarm port available on the ESR6300. The IOS name for the alarm port is Alarm Contact 0.
The following configuration commands are available in IOS:
The configuration commands also have their equivalent “no” prefaces.
The following documentation is available:
■All of the Cisco ESR6300 documentation can be found here:
https://www.cisco.com/c/en/us/support/routers/6300-series-embedded-service-routers/tsd-products-support-series-home.html
Caveats describe unexpected behavior in Cisco IOS releases. Caveats listed as open in a prior release are carried forward to the next release as either open or resolved.
Note : You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. If you do not have one, you can register for an account.
For more information about the Cisco Bug Search Tool, see the Bug Search Tool Help & FAQ.
In release 17.5.1, CME works only in Network-Advantage, not in Network-Essential.
Symptom : Up through release 17.4.1, CME worked with both Network-Advantage and Network-Essential license levels.
Workaround : In the upcoming release 17.6.1 and beyond, CME will be supported on both license levels.
CAN bus baudrate set fails message seen during bootup in 17.5.1.
Workaround : This message is benign and has zero functional impact. The message will be suppressed/hidden in the upcoming release 17.6.1.
■To receive timely, relevant information from Cisco, sign up at Cisco Profile Manager.
■To get the business impact you’re looking for with the technologies that matter, visit Cisco Services.
■To submit a service request, visit Cisco Support.
■To discover and browse secure, validated enterprise-class apps, products, solutions and services, visit Cisco Marketplace.
■To obtain general networking, training, and certification titles, visit Cisco Press.
■To find warranty information for a specific product or product family, access Cisco Warranty Finder.
Modifications to this product not authorized by Cisco could void the FCC approval and negate your authority to operate the product.
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 of this document are considered uncontrolled. See the current online version for the 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.