Cisco LMS 4.2 Appliance on VMware vSphere 4.0

Hi all,
I'm currently trying to install the Cisco LMS 4.2 Appliance on a VMware vSphere 4.0 environment.
I'm following the http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2/install/guide/instl.html#wp1689675
guide.
I downloaded the Cisco_Prime_LAN_Management_Solution_4_2.iso and I started the server.
I get this screen and I choose option 1:
A Welcome message appears:
Welcome to Cisco Prime LAN Management Solution 4.2
To boot from hard disk, press <Enter>
The following options appears:
•[1] Cisco Prime LAN Management Solution 4.2 Installation
This option allows you to perform installation of LMS 4.2.
•[2] Recover administrator password
This option allows you to recover the administration password. Follow Step 3 to Step 17 of Recovering Admin Password on Soft Appliance Installed on VMware, to recover the administration password.
•<Enter> Boot existing OS from Hard Disk
This allows you to boot up the existing OS available in the hard disk.
However, unlike the installation on my laptop (using VMware Workstation) I cannot get to this part:
Enter the following configuration details of the server:
•Hostname
•IP Address
•Subnetmask
•Gateway
•DNS Domain
et cetera
What follows looks like an installation to me.
When this stops I get a
localhost login:
I cannot enter Setup as I get a password statement afterwards.
Can somebody please help me as I'm having no idea what went wrong..
Many thanks in advance.

Thanks for your help, Marvin.
We went ahead with the .ova file and it worked alright.
We also did a little test and it seems that the .iso file does work on some VMware platforms. Our test environment had a VMware vSphere 4.1. When we started a VM with the same specs and the ISO file mounted, the installation did succeed.

Similar Messages

Where i can get a Cisco VMware Vsphere ESXi 4.1 update 1 installable media

Hi All,
can someone from cisco tell me how to get cisco vmware vsphere ESXi 4.1 update 1 that was certified by Cisco ?
because the last release from the vmware website still 4.1 without update 1.
http://downloads.vmware.com/d/details/esxi41_cisco_oem_iso/ZHcqYnRkdHdiZCpwcA==
Thanks.
Berwin H.

Sorry for any spelling errors:
What is working well for us, is to always get the latest ESX(i) release from vmware, apply all patches and then make sure to install the newest drivers for Cisco fnic (hba) and enic (lan) that can be found on the vmware site.
During our first UCS upgrade (we did not have installed the Cisco drivers) we experienced some issues. A lot of our VMs lost connectivity to storage for about 2-3 minutes during the reboot of the primary FI. After opening a support request at vmware and Cisco, vmware sent us a newer fnic driver, as the standard driver included in the ESX iso did not handle hba failover very well.
Since that upgrade we always keep up to date the enic and fnic drivers for Cisco UCS. They can be found on the VMWare ESX download site.
Newer drivers are also available on the Cisco UCS driver CD, but those are not yet signed by vmware, so it may be a better idea to use those tested by vmware.
Since we are handling ESX updates like this, every UCS upgrade and everything else worked like a charm and my pulse during upgrades got divided by 2
BTW: Also with other server manufacturers we could have saved us a lot of trouble if we simply had upgraded adapter drivers earlier.

How we archieve configuration for Cisco ASA 5500 series appliances

Hi,
We need to archieve configuration for Cisco ASA 5500 series appliances.
We have Cisco works LMS 3.0.1.
Device package installed is 4.2
Any help would be appricated.
Thanks in advance.
Samir

Hi ,
Thanks for your answer.
Right now we are using TACAS to login in to the ASA. That means we need single username and password to login via
Cisoworks. Am I correct ?
Waiting for your reply.
thanks,
Samir

Sequencing multiple versions of the VMWare vSphere client (and reducing the size of the final sequence)

Application Name: vSphere client
Application Version: 4.1, 5.0, and 5.5 (all in one package)
Company Name: VMWare
Sequencer Version: 5.0 SP1 or SP2
App-V Client Version Tested On: 5.0, 5.0 SP1, 5.0 SP2
Operating System Sequenced On: Windows 7 (64bit)
Pre-requisites: Orca
Client Operating Systems Successfully Deployed To: Windows 7 (64bit), Windows Server 2008 (64bit)
*Posted by non-Microsoft Employee: Cody Lambert (a Fortune 100 company)
If Posted by Microsoft Employee, the Corresponding KB Article Reference:
N/A
Steps to Prepare and Sequence the Application:
Phase 1: Prepare vSphere install to be used in your sequence (to be performed prior to sequencing)
Clear %TEMP% directory on machine you are using to prepare the install
Create a folder that will be referred to as "vSphereInstDir"
that install files are copied to
Download the vSphere 5.5 client from your vSphere management server
Run the installer for the vSphere Client
Once at the Language Selection portion of the installer,
using windows explorer browse to the %temp% directory and copy the files that were just created when the vSphere installer extracted to a directory (name it vSphereInstDir)
Kill the installer
Find VMware-viclient.exe in the files you just copied
and run it
Once at the "Welcome to the installation
wizard" stage of the installer, using windows explorer browse to the %temp% directory and copy the files that were just created into the vSphereInstDir
Kill the installer
Find the VMware vSphere Client 5.5.msi in the vSphereInstDir,
in the second set of files you copied over
Using Orca, open the VMware vSphere Client 5.5.msi
Drop the following rows from the msi (some of the rows may have additional text at the end of the names) (InstallExecuteSequence/VM_InstallHcmon,
InstallExecuteSequence/VM_InstallHcmon_SetData,
InstallExecuteSequence/VM_InstallUSB,
InstallExecuteSequence/VM_InstallUSB_SetData,
InstallExecuteSequence/VM_InstallUSBArbritrator,
InstallExecuteSequence/VM_InstallUSBArbritratorSetData,
InstallExecuteSequence/VM_StartUSBArbSvc)
Save the VMware vSphere 5.5.msi in place
Copy the vSphereInstDir to a network location that
can be used during sequencing on your Sequencer
Phase 2: Sequence the vSphere Client
Pre-requisites: All of the latest available VC++ redist (x64 and x86) are installed on the Sequencer VM
Copy vSphereInstDir to your temporary install directory on your Sequencer (mine is C:\temp)
Start up the Sequencer
Click Create a New Virtual Application Package
Click Next with Create Package (default) selected
Click Next on the Prepare Computer screen, taking
note of any findings
Click Next with Standard Application (default) selected
Choose Perform a custom installation, then click Next
Input the Virtual Application name (vSphere Client
5.5 for example)
Enter the Primary Virtual Application Directory (C:\vSphere55
for example) and click Next
Using Windows Explorer find the Visual J# install (vjredist64.exe) in the vSphereInstDir you copied over. Install using defaults
Using Windows Explorer, find and install the vSphere client using the VMware vSphere Client 5.0.msi located in the vSphereInstDir you copied over.
Change the installation directory to use the Primary Virtual Application Directory you configured above (C:\vSphere55 for example). Install using
defaults
While the sequencer is still monitoring changes connect to the 4.1 environment to get the files needed. To do this, launch the vSphere client and connect
to your 4.1 environment. When prompted, choose RUN to install the files needed for the 4.1 environment.
While the sequencer is still monitoring changes connect to the 5.0 environment to get the files needed. To do this, launch the vSphere client and
connect to your 5.0 environment. When prompted, choose RUN to install the files needed for the 5.0 environment.
With the sequencer still monitoring changes, after the additional environments have been installed, delete all of the language folders from the install locations
that are not required. You will find that there are language folders in each of the different modules that are installed. Make sure look in every folder. This will free up approximately 300mb from the package.
When done, check the box to finish the sequence and continue cleaning up the sequenced application.
Known Issues/Limitations:
Functions that require the USB Arbritration Service will not work
Approximate Sequencing Time:
20 minutes
Descriptive Tags:
App-V, 5.0, VMWare, vSphere, Recipe, Guidance
Credit Due: Thanks to Rorymon and Aaron Parker for accurate information that allowed for me to put together this recipe.

Can you double check the that the following were removed from the MSI:
InstallExecuteSequence/VM_InstallHcmon
InstallExecuteSequence/VM_InstallHcmon_SetData
InstallExecuteSequence/VM_InstallUSB
InstallExecuteSequence/VM_InstallUSB_SetData
InstallExecuteSequence/VM_InstallUSBArbritrator
InstallExecuteSequence/VM_InstallUSBArbritratorSetData
InstallExecuteSequence/VM_StartUSBArbSvc

What's the difference between OEM and standart licensing of VMware vSphere for users?

Good day,
Could you please explain me,
What's the difference between OEM and standart licensing of VMware vSphere for users?

The difference is usually the support you get. With OEM versions you'll often get support from the OEM and not from VMware directly.
André

Cisco LMS 3.2 SYSLOG not storing after 10 days

Hi ,
Im facing one issue with Cisco LMS 3.2
Issue : The logs is generating only for 10 days and post that im not able to see the logs. I have not done any config changes. The only change i have done is i have completely reinstalled the LMS. i did multiple troubleshoot but not able to resolve this isse. It would be great If any some one is able to help me in this isse. Thanks.
Regards,
Juliet

Dear Vinod
Thanks for ur response and the problem has been resolved.
The purge policy was set to 60 days only .The problem in reports viewing setting.
Syslog folder under LMS would store syslog reports of both the device as well as applications for defined folder size , which in your case was 1 MB ( same can be viewed under log generator option). The older reports would get deleted from the folder upon reaching the limit.
The only way to view device syslog is under following option : Reports -> Reports Generator in LMS GUI where we will have to choose syslog with desired attribute.
Regards,
Juliet

Cisco LMS 4.0 Graph some time not coming

I have installed cisco lms 4.0.
I have added 10 devices, previously it was working fine, Since last few days some time syslog and graph are not coming. after every reboot on server it started working. It is happening on daily.plz help me out with permanent solution
and also i have added manualy one device 7609-s router but not able to see cisco view
Error:-
Cannot find applicable device package for 10.133.224.131.
This error could be due to one of the following:
- The device package for this device type is not installed.
- Device support for this device type is not available.
- You are trying to open a component inside a device.
To correct the problem, either install a device package for the device type, or open the parent device to manage the component.
In device attribute it is showing 868 integrated router, I had try to delete and add again but problem is still same...
Windows 2008 r2 standard
RAM-16 Gb, Swap memory 8096

Evrything looks good. Are you able to access LMS in the server itself? Try to install another browser on your server and try to login.
Try both :
http://x.x.x.x:1741
https://x.x.x.x:443
Share NMSROOT/MDC/tomcat/logs/stdout.log and stderr.log.
-Thanks

Vmware vsphere health check report v5.1.0

Hi,
I'm currently using the vmware vsphere health check report v5.1.0 script. I switched from another perl script to this and the report provide much more information. There is one thing that don't seem to work properly though..
I currently have a failed disk in my server and the report is showing "unknown" status next to 3 disk / disk day. If I run the other script I have used in the past, I have 3 alerts in red clearly showing that something has failed. Would any of you know why it's showing as unknown instead of critical in the report?
Old Script
o Disk or Disk Bay 15 Drive 15 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 15 Drive 15 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 15 Drive 15 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 15 Drive 15 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 15 Drive 15 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 14 Drive 14 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 14 Drive 14 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 14 Drive 14 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 14 Drive 14 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 14 Drive 14 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 13 Drive 13 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 13 Drive 13 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 13 Drive 13 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 13 Drive 13 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 13 Drive 13 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 12 Drive 12 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 12 Drive 12 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 12 Drive 12 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 12 Drive 12 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 12 Drive 12 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 11 Drive 11 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 11 Drive 11 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 11 Drive 11 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 11 Drive 11 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 11 Drive 11 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 10 Drive 10 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 10 Drive 10 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 10 Drive 10 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 10 Drive 10 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 10 Drive 10 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 9 Drive 9 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 9 Drive 9 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 9 Drive 9 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 9 Drive 9 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 9 Drive 9 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 8 Drive 8 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 8 Drive 8 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 8 Drive 8 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 8 Drive 8 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 8 Drive 8 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 7 Drive 7 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 7 Drive 7 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 7 Drive 7 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 7 Drive 7 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 7 Drive 7 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 6 Drive 6 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 6 Drive 6 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 6 Drive 6 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 6 Drive 6 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 6 Drive 6 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 5 Drive 5 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 5 Drive 5 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 5 Drive 5 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 5 Drive 5 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 5 Drive 5 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 4 Drive 4 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 4 Drive 4 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 4 Drive 4 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 4 Drive 4 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 4 Drive 4 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 3 Drive 3 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 3 Drive 3 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 3 Drive 3 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 3 Drive 3 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 3 Drive 3 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 2 Drive 2 0: Drive Fault - Assert: 0
o Disk or Disk Bay 2 Drive 2 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 2 Drive 2 0: In Critical Array - Deassert: 0
o Disk or Disk Bay 2 Drive 2 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 2 Drive 2 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 1 Drive 1 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 1 Drive 1 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 1 Drive 1 0: In Critical Array - Assert: 0
o Disk or Disk Bay 1 Drive 1 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 1 Drive 1 0: Rebuild In Progress - Deassert: 0
o Disk or Disk Bay 0 Drive 0 0: Drive Fault - Deassert: 0
o Disk or Disk Bay 0 Drive 0 0: Predictive Failure - Deassert: 0
o Disk or Disk Bay 0 Drive 0 0: In Critical Array - Assert: 0
o Disk or Disk Bay 0 Drive 0 0: In Failed Array - Deassert: 0
o Disk or Disk Bay 0 Drive 0 0: Rebuild In Progress - Deassert: 0
New Report
BIOS 1 ABR Status 0: Unspecified - Deassert
0
OK
BIOS 1 Firmware Error 0: Unspecified - Deassert
0
OK
BIOS 1 Firmware Error 0: Unspecified - Deassert
0
OK
Cooling Unit 1 Cooling Zone 1 0 - Fully redundant
0
OK
Cooling Unit 2 Cooling Zone 2 0 - Fully redundant
0
OK
Cooling Unit 3 Cooling Zone 3 0 - Fully redundant
0
OK
Disk or Disk Bay 0 Drive 0 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 0 Drive 0 0: In Critical Array - Assert
0
UNKNOWN
Disk or Disk Bay 0 Drive 0 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 0 Drive 0 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 0 Drive 0 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 1 Drive 1 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 1 Drive 1 0: In Critical Array - Assert
0
UNKNOWN
Disk or Disk Bay 1 Drive 1 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 1 Drive 1 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 1 Drive 1 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 10 Drive 10 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 10 Drive 10 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 10 Drive 10 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 10 Drive 10 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 10 Drive 10 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 11 Drive 11 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 11 Drive 11 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 11 Drive 11 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 11 Drive 11 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 11 Drive 11 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 12 Drive 12 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 12 Drive 12 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 12 Drive 12 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 12 Drive 12 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 12 Drive 12 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 13 Drive 13 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 13 Drive 13 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 13 Drive 13 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 13 Drive 13 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 13 Drive 13 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 14 Drive 14 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 14 Drive 14 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 14 Drive 14 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 14 Drive 14 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 14 Drive 14 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 15 Drive 15 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 15 Drive 15 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 15 Drive 15 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 15 Drive 15 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 15 Drive 15 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 2 Drive 2 0: Drive Fault - Assert
0
UNKNOWN
Disk or Disk Bay 2 Drive 2 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 2 Drive 2 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 2 Drive 2 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 2 Drive 2 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 3 Drive 3 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 3 Drive 3 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 3 Drive 3 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 3 Drive 3 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 3 Drive 3 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 4 Drive 4 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 4 Drive 4 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 4 Drive 4 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 4 Drive 4 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 4 Drive 4 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 5 Drive 5 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 5 Drive 5 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 5 Drive 5 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 5 Drive 5 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 5 Drive 5 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 6 Drive 6 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 6 Drive 6 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 6 Drive 6 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 6 Drive 6 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 6 Drive 6 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 7 Drive 7 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 7 Drive 7 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 7 Drive 7 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 7 Drive 7 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 7 Drive 7 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 8 Drive 8 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 8 Drive 8 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 8 Drive 8 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 8 Drive 8 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 8 Drive 8 0: Rebuild In Progress - Deassert
0
OK
Disk or Disk Bay 9 Drive 9 0: Drive Fault - Deassert
0
OK
Disk or Disk Bay 9 Drive 9 0: In Critical Array - Deassert
0
OK
Disk or Disk Bay 9 Drive 9 0: In Failed Array - Deassert
0
OK
Disk or Disk Bay 9 Drive 9 0: Predictive Failure - Deassert
0
OK
Disk or Disk Bay 9 Drive 9 0: Rebuild In Progress - Deassert
0
OK

Thank you for the follow up. I do understand that a completly unreadable disk might throw an unknown status but the status is different from one report than the other. On one side, it clearly shows in red that the disk has something and on the side, it just throws a "I don't know what's going on with the disk". I ran both report the same day and i'm expecting some red in the report to warn me if a disk fail.
Is there a way to change that behavior from the health check script?

Cisco LMS 4.0.1 to Prime Infrastructure 2.x Upgrade

Hello,
we are using Cisco LMS and want to upgrade to Cisco Prime Infrastructure.
Now we have received the following license update: L-L-PI2X-100-U - LMS to Prime Infrastructure 2.x Upgrade 100 Device
and I wonder what is the best way to upgrade.
After a long search I found the following document on cisco:
http://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/prime-infrastructure/guide-c07-729990.html#wp9000727
There is only the talk of the upgrade from 4.2 LMS to Prime.
The problem is that we can not update to version 4.2 because of an error. Thats one reason why we need to upgrade to prime.
Is the only possibility now to export databases?
thanks in advance

Hi Heiko,
Upgarding from LMS 4.0.1 to LMS 4.2 , you need a New Licesne . Are you getting that error..
Upgarding from LMS to PI is alomost like a new Installation of PI. because only thing you can IMPORT from LMS to PI is the device list .
you can download the software from the below link:
http://software.cisco.com/download/release.html?mdfid=284422771&flowid=45323&softwareid=284272932&release=2.0.0&relind=AVAILABLE&rellifecycle=&reltype=all
Installation link:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-0/install/guide/Cisco_PI_Hardware_Appliance_Installation_Guide/cpi_higmain.html
hope it will help
Thanks-
Afroz
[Do rate the useful post]
****Ratings Encourages Contributors ****

Cisco lms - backup out of the box

when using cisco lms 4.2.5 linux version, what would be the best way to backup the config files out of the box?
what i'm lookin for is a way to take the shadow folder to another box for disaster recovery.

Hi, i found this solution to work very well for exporting files out of the box:
As user root:
1) on cisco-lms install sshfs, which lets you mount a folder on a remote box through sftp:
install in the following order:
rpm -ivh fuse-libs-2.7.4-8.el5.x86_64.rpm
rpm -ivh fuse-2.7.4-8.el5.x86_64.rpm
rpm -ivh fuse-sshfs-2.5-1.el5.rf.x86_64.rpm
2) mount
mkdir /mnt/backup
sshfs root@<remote-linux-box-ip>:<remote-folder> /mnt/backup -o allow_other
3) rsync with cron
00 1 * * * rsync -r -v /var/adm/CSCOpx/files/rme/dcma/shadow/* /mnt/backup/ >> /root/rsync.log 2>&1

Error in Cisco LMS

Hi,
I get this error when i run some actions in CISCO LMS 3.2 i.e if I click in Campus Manager - Start Data Collection. it gives error " you are not access to request this action ".
What can be the problem?
Please find the attachment for your reference.
Please Suggest. waiting for your prompt reply.
Thanks

to fix the database issue , you need to reintilaze the ANI database:
1) Stop the daemon manager
"net stop crmdmgtd"
2) Go to NMSROOT\CSCOpx\bin.
NMSROOT\bin\perl.exe NMSROOT\bin\dbRestoreOrig.pl dsn=ani dmprefix=ANI
for linux:
/opt/CSCOpx/bin/dbRestoreOrig.pl dsn=ani dmprefix=ANI
3) Wait for a few minutes before starting the CW daemons again:
"net start crmdmgtd" (wait for at least 5 minutes before using CW again)
Thanks-
Afroz
***Ratings Encourages Contributors ***

Alerts from Cisco LMS

Dears I have some concerns about SNMP and Cisco LMS :
Our network device sent a LINK DOWN trap to CISCO LMS followed by LINK UP trap . I can see these messages from the device logs . My questions is :
1-If the device is configured correctly to send snmp traps .And the syslog is showing both messages (LINK DOWN , LINK UP) then we can say the device is sending the snmp traps ?
2-Why the LINK UP trap is missing in Cisco LMS .. What should we check to make sure LMS is sending and receiving these alert in proper way ???
Thanks in advance .

Hi ,
-If the device is configured correctly to send snmp traps .And the syslog is showing both messages (LINK DOWN , LINK UP) then we can say the device is sending the snmp traps ?
Syslogs are different from SNMP traps , If you are seeing syslogs for linkup and linkdown ,it does not mean that device is sending the SNMP traps as well.
2-Why the LINK UP trap is missing in Cisco LMS .. What should we check to make sure LMS is sending and receiving these alert in proper way ???
You can verify the snmp trap by packet capture
Thanks-
Afroz
****Ratings Encourages Contributors ****

VMware Vsphere 5.0

Hi,
We are looking for suggestions and advice from the users who are running Oracle EBS R12 in VMware Vsphere 5.0 environment.
Thanks & Regards
Chakrapani.S

Helping the little guys think big!
http://www.microage.com/data-center-refresh-and-server-virtualization-provides-big-benefits.html
This topic first appeared in the Spiceworks Community

Upgrading from cisco LMS 3.0 to a latest version

Hello,
Upgrading from cisco LMS 3.0 to a higher version.
Whatdoes it require?.
What is the current version?
What do we need for upgrading?
Are there specific codes or new need to buy new products?
In case of buying new products, which are the configurations?

H Malik,
You are correct! Latest version is Cisco prime LMS 4.2. There is no direct upgrade from LMS 3.x to LMS 4.x.
The procedure is simple:
Take backup orf old LMS --> Un-install (if same machine)--> Install new LMS --> Restore backup to get old data.
You would need to purchase new license for it.Cisco Prime LMS is now part of the Cisco Prime Infrastructure bundle and is not orderable separately. Cisco Prime Infrastructure bundle follows a size-based incremental licensing model. Device licenses can be combined and added when applied to a single server installation instance. Customers have the option of adding incremental licenses for additional devices as their network grows.Refer to the Cisco Prime Infrastructure Ordering Guide located at http://www.cisco.com/go/primeinfrastructure for the exact part number that matches your requirement and placing the order.
Currently even SmartNet or SAS contracts does not cover major upgrades from LMS 2.x and 3.x; an upgrade part number will need to be purchased to move to Cisco Prime LMS 4.2. These upgrade part numbers reflect a significant discount to protect customers' investment in the Cisco Prime product line.
The data migration process will vary depending on the LMS version from which the data need to be migrated. Migrating data to LMS 4.2:
• LMS 4.2 supports local upgrade or direct inline upgrade only from LMS 4.0.1 and LMS 4.1.
• LMS 4.0 customers are encouraged to install LMS 4.0.1 before doing inline upgrade to LMS 4.2.
• LMS 3.2 and LMS 3.2 Service Pack 1 customers can do a remote upgrade through the LMS backup and restore mechanism.
• LMS 3.1, LMS 3.0, LMS 3.0 December 2007 Update, LMS 2.6, and LMS 2.6 Service Pack 1 customers need to do a remote upgrade to LMS 4.0.1 and then upgrade to LMS 4.2.
-Thanks
Vinod

Upgrade Cisco LMS to PI

We currently operate Cisco Prime LMS v4.1 and we're looking to upgrade Cisco PI (Prime Infrastructure) in the next few weeks.
Is there an upgrade path from Cisco LMS to PI? The reading I have completed seems to indicate that an upgrade can only be completed from Cisco NCS.
If I need to perform a new install of PI, can I somehow Migrate / Import my existing device database and config into the new software? I have configured some syslog fault rules for e-mail notification, config templates, custom reports, etc, that I would also like to keep and not necessarily recreate.
Thanks.

As cwallin noted, LMS 4.2.2 patch added the ability to migrate some information from LMS to PI.
Most customers would not be well-served by migrating a mature LMS implementation to PI at this time due to the fact that PI does not yet have feature parity with LMS, Even PI 2.0 (due out in a couple of months) will not have complete feature parity.
See this link for a current comparison.

Cisco LMS 4.2 Appliance on VMware vSphere 4.0

Similar Messages

Maybe you are looking for