Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Upgrade to LMS 3.0 from 2.6

I just received LMS 3.0. I would like to do a "clean install" as opposed to an upgrade. I could use some guidance on how to completely uninstall 2.6 and any other system preparation tasks prior to installing 3.0. Has anyone else done this (ie - unistall 2.6 and install 3.0)?? What's the best practice here?

Thanks for your assistance.

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Upgrade to LMS 3.0 from 2.6

This is a known bug (CSCsk19350). A patch is available from http://www.cisco.com/cgi-bin/tablebuild.pl/cwa10 .

8 REPLIES
Cisco Employee

Re: Upgrade to LMS 3.0 from 2.6

Just do the uninstall as you would normally, then remove the left over NMSROOT directory when you're done. If this is Windows, then reboot after that.

New Member

Re: Upgrade to LMS 3.0 from 2.6

Ok - thanks for that. One other thing - Are there any registry keys/entries I need to be concerned with left over from the uninstall?

Cisco Employee

Re: Upgrade to LMS 3.0 from 2.6

No, there shouldn't be if the uninstall is done properly. If that fails, you can contact the TAC for an executable that will completely clean the system of CiscoWorks.

New Member

Re: Upgrade to LMS 3.0 from 2.6

J,

Thanks for all your assistance. I have just 1 last issue I need help with so I can can move forward on the LMS 3.0 install tomorrow.

We are not using DNS for our devices, I have created a Hosts file though with the IP's and device names I want to use.

What do I need to do on the install so that DFM will use the device names (rather than IP addresses) for the "Managed Object = " field in the email notifications? Heres what we get now in 2.6:

EVENT ID = 000HD17

ALERT ID = 0000HWO

TIME = Thu 22-Nov-2007 05:01:53 PST

STATUS = Active

SEVERITY = Critical

MANAGED OBJECT = 10.255.255.82

MANAGED OBJECT TYPE = Routers

EVENT DESCRIPTION = OperationallyDown::Component=CARD-10.255.255.82/5 [0/1/0] [Unknown];SystemName=10.255.255.82;Status=CRITICAL;StandbyStatus=NOTAPPLICABLE;Location=Slot:0/1/0|Serial#:0|HwVersion:1.3|SwVersion:|;Description=Unknown;

CUSTOMER IDENTIFICATION = VReda

CUSTOMER REVISION = 1a

Is the hosts file adequate or do I need to do anything else? Also - what do I check (or uncheck) as far as using reverse dns, use host name, use system name (whats the diff?), etc... in the setup?

Thanks again for all your help.

Charles

Cisco Employee

Re: Upgrade to LMS 3.0 from 2.6

A hosts file should be adequate. You can check hostname resolution using the resolver.pl utility that is distributed with LMS:

NMSROOT/bin/perl NMSROOT/bin/resolver.pl HOSTNAME

NMSROOT/bin/perl NMSROOT/bin/resolver.pl IPADDRESS

You want forward and reverse resolution to be consistent.

New Member

Re: Upgrade to LMS 3.0 from 2.6

J,

I installed LMS 3.0 fine, then updated to Campus 5.0.1 and DFM 3.0.1 - now when I go to Server Setup there are red X's (instead of green check marks) under column "version supported" . What am I missing here? The installs of both patches seemed like they went fine with no issues.

Cisco Employee

Re: Upgrade to LMS 3.0 from 2.6

This is a known bug (CSCsk19350). A patch is available from http://www.cisco.com/cgi-bin/tablebuild.pl/cwa10 .

New Member

Re: Upgrade to LMS 3.0 from 2.6

That fixed it - thanks!

173
Views
0
Helpful
8
Replies