We are running Cisco Prime LAN Management Solution version 4.2.3. Any idea when we can expect to see an LMS device package for the new 3850 switches? Right now we can't capture the configuration on a test 3850 and some things get reported incorrectly in fault manager.
When trying to sync the configuration for the switch the job fails with the following error: CM0205 Device package for xxx.xxx.xxx.xxx not found Check whether the specified package path - "D:/PROGRA~2/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/lib/pkgs" is correct Action: Check if required device packages are available
I keep the packages up to date. I checked and I have the packages completely up to date as of today. Looking at the list of supported devices (thanks for the link btw), it makes me think there may be some bug or misconfiguration issue that we need to take up with Cisco support. The error message about not finding an RME package should give them some guidance on what to look at.
Yes, that looks like an oversight. Open a TAC case and they should add the -L models. I got a Nexus 7k card added via that method last year.
BTW, LMS keys on the snmp OID to determine what it's seeing. If the product's OID isn't in the definition file, it will not be unrecognized.
Message was edited by: Marvin Rhoads - fixed last sentence to add "not"
As an update to this, Cisco has now registered CSCuj61704 to cover this problem. I will try to remember to update this thread when Cisco provides a fix to LMS. Surely others must be using the 3850-24P-L model with LMS. Not being able to capture the configuration in LMS is a serious issue.
Thanks for the update.
Sadly, not everyone avails themselves of all the features nor checks their tools to see they're working as they should. It would be nice if Cisco's QA (either on the hardware BU or the network management BU) caught all of these but they don't. Cisco is hardly alone in this - all tool vendors have opportunities to improve in this regard. Anyone who's searched on SolarWinds Thwack forum and found 3 year old unanswered questions that remain as features not implemented or outright bugs several major releases later can attest to that.
Customers like yourself holding them accountable gets resources put on the tasks.