LMS 2.6 / RME 4.0.6 : Update device packages

Hi All,
I want update device packages for the device Unknow c3560v2 and ME2400 on ciscoworks lms 2.6.
CCS= version 3.0.6
CM= version 4.0.10
CV = 6.1.5
DFM = 2.0.7
IPM = 2.6.0
RME = 4.0.6
The server doesn't have access internet so i downloaded files and copy this on directory psu.
1) I've tried directely upgrading the device package in RME, but it failed. He want file mdf v1.22 and the version is V1.20.
2) I've upgrading CiscoView for device, it's ok
3) I've upgrading Campus Manager with version 4.0.13, it's ok
4) I've tried upgrading the device package in RME, but it failed. He want file mdf v1.27 and the version is V1.25 after upgrade Campus.
I don't find on site cisco the version 1.27 of mdf, where i can found this file ?
I have the version 1.56 but it's compatible for LMS 2.6 and RME 4.0.6 ?
How can uninstall a version of mdf if I have a problem with this version?
thanks

Indeed. It does look like the only MDF available is 1.52 for CS 3.0
I also saw the note:
You must install Campus Manager 4.0.13 and MDF 1.27 before installing CMDeviceUpdates 2.0.
RME 4.0.6 Release Notes
FYI. LMS 2.6 is EOL. As such I suggest you contact your account team to see if they can acquire it for you.
Thanks.

Similar Messages

Can't update device package for adobe DC in cd photo shop CS3 beta)

i've installed device central from CD Photoshop CS3 BETA ,
the problem is i can not install new device package for the file
that download from net , and it always shown ( the file update is
too new for this version of adobe device central ).... somebody
help me please ?

I am pretty sure that the Device Central that came with
Photoshop CS3 BETA is different from the official release of Device
Central that comes with CS3 products.
I had Photoshop CS3 BETA and DC working. Then I bought a
licenced copy of Flash CS3 and Device Central. The new device
package installed perfectly on the newer version of DC. However,
now that I have installed the new Device Central, I can't launch DC
from Photoshop CS3 BETA—it gives me an error.
That said, DC works great—with the update—but
only via Flash CS3 (or some other official launch product).

CiscoWorks LMS 3.2 unable to update device packages

Chaps,
This is a new install of LMS 3.2 with the Campus Manager patched to 5.2.1.
I'm unable to install any new device updates, if I use the GUI and Check for Updates then it says that none are available. The Device Count Type for Campus Manager is 0 although and my 3750X stacks are not supported.
Any ideas?
Jim

Try to install the update manually. Open CLI on the server, navigate to $NMSRoot\bin directory and execute the commands:
1. PSUCli.bat -p cm -dst -download CMDeviceUpdates , On providing cisco.com credentials CMDeviceUpdates.zip will be
downloaded to "\cm" location. For example if is
C:\psu_download then package will be under C:\psu_download\cm.
2. Install the package by executing below command:
PSUCli.bat -p cm -install -src\cm CMDeviceUpdates

LMS 3.2 RME Device Update failed

Hello experts,
I got a new error on my LMS 3.2 with RME 4.3.1
I can´t install any of the RME Device updates.
e.g. : "Installation failed for product [Resource Manager Essentials] with message : com.cisco.nm.xms.psu.packagemgmt.InstallerException: Repository in use. Another Package Support Updater client session may be modifying device support."
I looked up for a .lock file in my CW dir but there is no one.
NMSROOT/Psu.Lock and NMSROOT/www/classpath/com/cisco/nm/xms/psu/Psu.Lock does not exist.
There are no other .lock files in the CW dir and subdirs.
I attatched a psu.log file. Maybe u will see the failure.
What I tried:
- Restart daemon
- install from cisco.com
- install from local dir
... everytime the package installation failed.
Bye,
Patrick

You will need an identical server (RME 4.3.1) with an updated/healthy package repository. If you have that, you can follow these steps to regenerate maps:
1. Shutdown daemons:
net stop crmdmgtd
2. On the bad server, delete all .zip files under the two RME package repositories:
NMSROOT\www\classpath\com\cisco\nm\xms\psu\pkgs\rme
NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\lib\pkgs
3. Copy all of the packages under one of the above locations on the good server to both of these locations on the bad server.
4. Delete your bad rme*.map files under NMSROOT/www/classpath/com/cisco/nm/xms/psu/maps/ and replace them with the good ones.
5. Restart daemons:
net start crmdmgtd

LMS 3.2: RME failed archive with Nexus 5010

Hi,
LMS 3.2, RME 4.3.1, dev packages updated, Windows.
We would like to archive the configuration of the Nexus 5010 switches. Due to authentication with Radius based on tokens we're not able to use telnet/SSH and therefore we only can use SNMP WRite in combination with TFTP. But, this is not working at all. Other systems like 3750 works fine. Is there a difference between Catalysts IOS and nexus NXOS?
I searched the forum and found this:
https://supportforums.cisco.com/message/663481#663481
upgrade to LMS 2.6, archive config not working anymore
We ship and start a TFTP server by default on Windows. You must have an SNMP read-write community string configured on your devices, and entered in DCR for TFTP config fetches to work. Additionally, udp/69 must be open between device and server.
The easiest way to troubleshoot this kind of problem is to start a sniffer trace on the LMS server (using Device Center > Packet Capture). Filter on all traffic to one of the failing devices. Then, run a Sync Archive job for that same device. When it fails, the sniffer trace will indicate what the problem is
Regards
Ad Olsthoorn

Hi Lavramov,
Yes I'm quite sure, I installed the required packages acoording to the Nexus.RME431.v2-2.readme.pdf manual. the manual tell me to install the following (see also attachement).
To install the Cisco Nexus Series Package, you must install the following dependent packages:
- SharedDcmaSS.RME431.v2-2.zip
- SharedInventoryMDS.RME431.v1-5-1.zip
- SharedSwimMDS9000.RME431.v1-6-1.zip
- SharedNetshowSS.RME431.v1-1.zip
regards
Ad

RME 4.0.6 Device Package update failure

Hi,
i have downloaded a lot of new device packages for the RME 4.0.6. If i install this packages i get the following error message.
Installation failed for product [Resource Manager Essentials] with message : com.cisco.nm.xms.psu.packagemgmt.InstallerException: Repository in use.
Another Package Support Updater client session may be modifying device support.
I searched for the psu.lock file but i couldn't find this file. How can i fix this without reinstalling the lms?
AndrÃ©

Hi,
i have attached the psu.log file. There is no .lock file, i've checked this again. I tried again to update the device packages
After 1 hour i stopped the update.( normaly an update take max. 10 minutes. During the device package update i could see the the psu.log file was going into a loop. It starts at 0 kbytes -> growing to nearly 950kbytes and than it starts again at 0 kbytes
Andre

LMS 4.2 fails Device Package Update

Hallo,
Device Package Update fails with this error:
Error while downloading package information from Cisco.com for the selected products. See the d:/CSCOpx/log/psu.log file for details.
PSU.log shows:
ERROR [RemoteRepSync : downloadPsuHeadersAsXml] : VDSException thrown com.cisco.nm.xms.vds.VDSException: CcoDownloadAdapter::getXmlFileList():IOException:connect timed out
best regards
Alex

What is the exact model of 3850 switch you're trying to monitor?
Following are the supported models :
Device Name
sysObjectID
Supported Software Version
Support Type
Device Name
sysObjectID
Supported Software Version
Support Type
Cisco Catalyst 3850-48P-E Switch
1.3.6.1.4.1.9.1.1641
Device Update
Cisco Catalyst 3850-48P-S Switch
1.3.6.1.4.1.9.1.1643
Device Update
Cisco Catalyst 3850-24P-E Switch
1.3.6.1.4.1.9.1.1642
Device Update
Cisco Catalyst 3850-24P-S Switch
1.3.6.1.4.1.9.1.1644
Device Update
Cisco Catalyst 3850-24U-E Switch
1.3.6.1.4.1.9.1.1767
03.11.35.EMP
Device Update
Cisco Catalyst 3850-48U-E Switch
1.3.6.1.4.1.9.1.1768
03.11.35.EMP
Device Update
If it is 3850-24p-L, it can be :
CSCuj61704 No support for 3850-24p-L in LMS 4.2.3
Try updating your mdf device package as well. Device package for Common Services.
For current Nexus device package issue, each device package is not individual, but has some dependant packages. Without which they are tend to fail during installation check.
You can select all the available device packages and try to install. It seems you dont have SharedDcmaIOS (3.1.7) installed and hence the package is failng due to pre-requisite.
You have to install each package which fails which consistancy check on other packages.
For mdf package update, you can select common service as well and check for update.
There may be some 3850 device packages already available, please share output of following command for us to see :
NMSROOT/bin/psucli -p rme -q -all
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

How to update a device package in LMS 4.1

I am adding SUP 2 T's into the network and need to have LMS monitoring them. I have not yet been able to figure out where to upgrade the device package so that I can add the SUP 2 T's

Yeah, for Inventory Config And Image Management (the traditional RME functions, in LMS 3.x lingo), you have to perform a separate "Software Update" (vis-a-vis Device Update, which is apparently for CiscoView). That's described in the same aforementioned URL, a little further up, Admin -> System -> Software Center -> Software Update:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/user/guide/admin/swcenter.html#wp1096852
The following page describes, in not-so-clear terms, whether it's Software Update or Device Update that's needed to get newer hw/sw recognized by the various pieces of LMS 4.1.
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/device_support/table/lms41sdt.html

LMS 3.0.1 with DEC 2007 update

Hi,
I have installed LMS 3.0.1 with Dec 2007 update,i have done custom installation and after that i installed 2007 update,after completing installation and update ,when i start LMS the process of LMS are not coming up for very very very long time and all process are down even DCR server is down,attachd are the logs,
Pls suggests Experts,
Thanks in Advance

It sounds like you may still have another process failure if processes take a long time to startup. Post the output of the pdshow command from the server.
As for logs, all of them are found under NMSROOT/log on Windows. Some of the logs are named after the processes to which they correspond (e.g. DCRServer.log). However, you shouldn't typically look through logs. Many of them will contain "normal" errors.

LMS 3.2 - RME 4.3.1 Sync archive fails

Hi,
Sync archive fails for some of my devices.
This is the message :
*** Device Details for .... ***
Protocol ==> Unknown / Not Applicable
Selected Protocols with order ==> Telnet,TFTP,SSH,RCP,HTTPS
Execution Result:
CM00139 Could not archive config Cause: Action: Verify that device is managed and credentials are correct. Increase timeout value, if required.
Check device credential is OK (Telnet + SNMP V2)
This device is Cisco Systems WS-C6009.Cisco Catalyst Operating System Software, Version 7.4(3). (sysObjectID : enterprises.9.5.39)
I have modified the "Maximum time to wait for Job Results per device (seconds):" to 240.
What could be wrong?
Thanks in advance

Resolution Summary:Checked the dcmaService.log and found the following recurring statements.
com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,406,Descr = 12.2(50)SE
[ Tue Oct 26 15:58:45 CDT 2010 ],DEBUG,[main],com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,405,suppSysId = .1.3.6.1.4.1.9.1.927
[ Tue Oct 26 15:58:45 CDT 2010
Checked that the device IOS was well above the version specified in the logs, so thought may be an issue with the device packages.
Checked the mdf version was 1.25 which came as default when we install LMS 3.2, so upgraded the mdf version to 1.45.
Still the issue didn't got solved, so upgraded the RME device packages and now the archive job was successful.
Message was edited by: Dheeraj Gera

LMS 3.2 RME 4.3.1 Archive Jobs hang

LMS 3.2 Windows 2003 R2 8Gig RAM
Managing ~4000 devices currently on LMS 3.1. Built new LMS3.2 server and patched to RME 4.3.1.
Import from csv file works fine and RME inventory collection/ Campus Manager Data Collection all works perfectly.
Archive Jobs hang (at random device #'s) after starting successfully.
I have tried restarting ConfigMgmtServer process, rebooting, even reinit CMF, RME and ANI db and starting from scratch but issue persists.
Are there any known issues with LMS 3.2 on Archive Jobs hanging or should I debug and open TAC case?

Resolution Summary:Checked the dcmaService.log and found the following recurring statements.
com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,406,Descr = 12.2(50)SE
[ Tue Oct 26 15:58:45 CDT 2010 ],DEBUG,[main],com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,405,suppSysId = .1.3.6.1.4.1.9.1.927
[ Tue Oct 26 15:58:45 CDT 2010
Checked that the device IOS was well above the version specified in the logs, so thought may be an issue with the device packages.
Checked the mdf version was 1.25 which came as default when we install LMS 3.2, so upgraded the mdf version to 1.45.
Still the issue didn't got solved, so upgraded the RME device packages and now the archive job was successful.
Message was edited by: Dheeraj Gera

LMS 4.1 Device Packages Update Installation

Hello, i used the software center to download latest device packages, all downloaded to PSU_Downloads folder , i want to know how to install them with GUI if possible , as i tried to use CLI but it seems that i'm using bad syntax.
Best Regards.

The cli syntax can be a bit tricky. If you have already downloaded the updates, you can perform the updates using the downloaded copies as your source. Please see step 2 of the procedure listed here, specifically:
To check for updates from a server, select the Enter Server Path radio button and enter the path or browse to the location using the Browse tab.

RME 4.3.1 & Nexus 7000 device package

I am have 27 devices that RME reports as "Out-of-Sync", among those some are Nexus 7K devices, with the sysObjectId .1.3.6.1.4.1.9.12.3.1.3.612, which according to the "Supported Device Table for LMS 3.2" is supported in RME 4.3.1.
Searching for device package with that sysObjectId I get no result in Common Services. However, when performing a "Device Update" with my CCO account, Ciscoworks tells me that "All the available package(s) at source location are already installed."
What do I have to do to get that device package?

Hi,
To check / download the latest RME Device Package for Nexus 7k support, please do the following :
1. Go to Common Services -> Software Centre -> Device Update and click on the hyperlink for 'CiscoWorls Common Services'
* You should see 2 packages listed - Device Data and MDF.
* The latest versions of these are 1.10 and 1.48 respectively.
* If you don't have the lateset versions installed, please run an update to install these.
2. Once you have the most up to date packages for Common Services installed, go to Common Services -> Software Centre -> Device Update and click on the number in the 'Device Type Count' collumn for Resource Manager Essentials. Filter the list of devices by Package Name = Nexus.
* Do you see sysObjectId .1.3.6.1.4.1.9.12.3.1.3.612 displayed ?
* What version of the Nexus device package do you have installed ? (The latest version is 2.5)
3. Even if you have the latest Nexus package installed, run a device update for RME so that you loaded the latest versions of all packages (I see there were some new updates for shared packages eg LibCommon as recent as 21st January 2011.
In terms of the devices being reported as 'Out-of-sync' , this means that RME has detected that the running configuration and the startup configuration on the device are different. This could be because RME doesn't have the most recent copy of either config or it is a real situation of the startup and running config being out of sync on the device. If you go to the Out-of-Sync Summary page, select the Nexus 7k's and click on 'Sync on Device' RME will run a job to login to the devices and execute a copy run start.
* If your Nexus 7k's are still reported as 'Out-of-Sync' after the job completes then we'll need to investigate further.
Regards
Derek Clothier

Device packages for LMS 3.2

Hello,
Can someone point me in the right direction to download device packages for LMS 3.2 for Solaris.
Thanks,
Tim
GSP

Hi Tim
Are you referring for device packages for RME ? If so which version of RME do you have ? You can downlaod device packages from CCO using this URL:
http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=4.3.1&mdfid=282635175&sftType=CiscoWorks+Resource+Manager+Essentials+Device+Package+Updates&optPlat=&nodecount=2&edesignator=null&modelName=CiscoWorks+Resource+Manager+Essentials+4.3&treeMdfId=268439477&treeName=Network+Management&modifmdfid=&imname=&hybrid=Y&imst=N&lr=Y
Hope this helps.. All the best..
Raj

RME unable to telnet to devices presenting "username:" prompt

In the network of my latest LMS 3.2 installation a lot of the devices is presenting a telnet prompt with a lowercase "u" in username. This seems to cause the RME to not be able to login to the devices. I remember from earlier that it was possible to edit a file on the LMS server to decide which prompts were acceptable. Does anyone know if this still is possible or how to solve this problem?

Many thanks for your input, it solved my problem
Do you also know what to do if there are several different prompts presented? Just add lines of USERNAME_PROMPT= in the file?

LMS 2.6 / RME 4.0.6 : Update device packages

Similar Messages

Maybe you are looking for