Customer has an 1801 running 15.0(1)M8 c180x-broadband-mz.150-1.M8.bin.
When they try to configure EEM from conf t they get an unrecognized command error.
Feature Navigator shows EEM as available in 15.0(1)M7. But Feature Navigator itself doesn't support M8. If you search for c180x-broadband-mz.150-1.M8.bin you get the following message "The Image Name you entered does not match any supported Cisco software releases in this tool. Please change the Image Name and search again. Thank you."
EEM technology notes say 3.1 is supported in Cisco IOS Release 15.0(1)M and later releases.
I guess the question is does M8 support EEM or is this a bug or do you need a license or similar to enable EEM functionality?
Opened TAC case - see response below. Customer needed to upgrade to Advanced IP Services.
This is not a bug. You have to understand that this tool is not 100% accurate (like with 15.0(1)M8). If you search for Embedded Event Manager (EEM) 3.0 in features, only ADV IP SERVICES and ADV ENTERPRISE feature sets will support it on an 1801. The discrepancy is only with Embedded Event Manager (EEM) 3.1.
Since 15.0(1)M8 is very new, the Feature Navigator is not updated with this version. But if we look the features using 15.0(1)M7 we can see Embedded Event Manager (EEM) 3.1 only. But if we choose an ADVANCED IP SERVICES feature set we see all these features:
So it could be a mis-configuration with this feature since it doesn’t make sense that it will support EEM 3.1 but not the previous versions. That’s why I think an upgrade to an ADVANCED IP SERVICES feature set is need it.
Since you have the required memory to upgrade to ADVANCED IP SERVICES I suggest you to do the upgrade and try again.
Inviting all network professionals in operations! We'd like to understand what would be valuable for you in a mobile application. Your response will help Cisco improve a product feature that could benefit you. Thanks!
Click here to take the sur...
Cisco’s software-defined wide area network (SD-WAN) solution allows user to quickly and seamlessly establish an overlay fabric to connect an enterprise’s data centers, branch and campus locations, as well as colocation facilities in order to imp...
1. Log into CLI of DNAC:
ssh maglev@< DNAC appliance IP> -p 2222
2. Run this curl command to get token to get member id:
curl -X POST -u admin:<admin user password> -H -V https://<CLUSTER-IP>/api/system/v1/identitymgmt/token
Enterprise Switching Business Unit is glad to announce Beta release 16.12.2 for all Catalyst 9200/9300/9400/9500/9600 and Catalyst 3650/3850 Platforms. This release is made available to allow users to test, evaluate and share fee...
Purpose of the document
This document describes the general recommendations or best practices when designing and deploying the Cisco SD-Access technology. The document assumes that the reader has a general overview of Cisco's SD-Access for Distributed C...