I have a new server that I want to load LMS 2.6 on. The cd's that I have are the full version of LMS 2.5 and the upgrade cd to 2.6. My question is do I still need to load the LMS 2.5 full version befor loading the LMS 2.6?
You need to load the LMS 2.5 CDs, then upgrade to 2.5.1, then upgrade to LMS 2.6. If your CDs are already at 2.5.1 (i.e. CS 3.0.3, RME 4.0.3, CM 4.0.3, DFM 2.0.3), then you can upgrade to 2.6 after installing the 2.5.1 CDs. If not, you'll need to download the 2.5.1 update from http://www.cisco.com/cgi-bin/tablebuild.pl/lms25 .
Yes I have the full version of LMS 2.5.1 and the upgrade to LMS 2.6 Ok so I do need to load the LMS 2.5.1 then once this is done with the who suit then run the upgrade LMS 2.6 on top of this one.
Should I go ahead and discover the network after installing LMS 2.5.1 and add the device's in manually for IPM before installing the upgrade LMS 2.6?
I would upgrade and patch everything to the highest level before starting to use the suite. This way you'll have all the bug fixes.
Ok I'll do this then. So there is not dependencys on 2.5.1 for the upgrade 2.6? So I load LMS 2.5.1 register it then automatically install upgrade LMS 2.6 then the patches correct... right.
You install LMS 2.5.1 from CDs. Once all the desired applications are installed, then reboot. Then insert the 2.6 CD (or download the 2.6 update patch). Apply the 2.6 update. When that is done, you can use Common Services > Software Center > Software Update to update all of the apps to LMS 2.6 SP1.
Would you happen to know why LMS 2.5.1 needs 80gb or more free space for LMS applications and data. Compared to LMS 2.6 which states it needs on 20gb or more free space for LMS applications and data?
On this same note is SAN supported with CiscoWorks? I'm needing to upgrade the blade server which is a HP Proliant BL 460cG1. This server will have duel fiber links to the SAN for redudancy.
LMS on SAN has not been officially tested. We always recommend locally attached storage. That said, I believe we do have a few customers running on SAN without issues.