The following features are not supported on the ESR6300 with software release 17.1.1:
■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.
■IOx Application access to serial port or USB-serial is not supported.
■Booting the golden configuration from a USB is NOT supported in this release.
■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.
■There is no WebUI support for Day 0 or Day 1 configuration
■For Security: No support for TLS, TrustSec, MacSec, CWS [Cloud Web Security], IDS/IPS.
This release has the following limitations or deviations for expected behavior:
■The WebUI Licensing Page is unsupported for release 17.1.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.1.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:
(config)#boot system flash msata:ios-image
■Receive a message 'unable to open bootflash:golden.bin (14)' during bootup.
Example: Pushing the reset button displays the unable to open message.
ESR-6300-CON-K9 platform with 4194304 Kbytes of main memory
MCU Version - Bootloader: 4, App: 10
MCU is in application mode.
Reset button push detected
unable to open bootflash:golden.bin (14)
This message is intended by design to inform the user they have not setup a golden.bin config file.