Veeam SPI 5.x license issue?

VMware monitoring with HP Operations Manager

Veeam SPI 5.x license issue?

Veeam Logoby apavil » Fri Feb 25, 2011 9:56 am

Yesterday the vcentre server was migrated to a different server.

Before the move, I had a 12 socket license so I had 6 ESX (out of 11) of 2 sockets monitored.

After I added the new VMWare server (I deleted the previous one) in nworks management Center/Connected Server tab/Connect to VMWare server popup, I was only able to tick 4 ESX.

The ESX are exactly the same as before, the VEM/VIC server as well.

If I untick all of them it still shows in the dashboard:

Total VC: 1
Total ESX: 11
Monitored: 0
Ignored: 11

Total sockets: 12
Used sockets: 4

So is it a bug or are licenses used not only when monitoring the ESX but also by other options by the VIC/VEM or the VMWare server?
Could it be that be pointing to a new server it reset some options and reenabled some extra collection/metric that would "consume" extra sockets?

Or is it possible that the VMWare server itself uses 4 sockets, as opposed to the previous one that had perhaps a smaller setup therefore did not use any sockets at all (I did not touch the VMware server so I admit I do not know much about their config).

I did the following:
1. Remove all servers under "Connected Severs" tab in the Management Center.
2. Delete the "maindb.xml" file (default location: "C:\Documents and Settings\All Users\Application Data\nworks\Management Center")
3. Re-add the servers you would like to monitor.

But same as before
apavil
Novice
 
Posts: 4
Liked: never
Joined: Fri Feb 25, 2011 9:41 am
Full Name: Antonin PAVIL

Re: Veeam SPI 5.x license issue?

Veeam Logoby Irina Simkina » Fri Feb 25, 2011 10:19 am

Hello!

you have made the correct steps:
1. Remove all servers under "Connected Severs" tab in the Management Center.
2. Delete the "maindb.xml" file (default location: "C:\Documents and Settings\All Users\Application Data\nworks\Management Center")
3. Re-add the servers you would like to monitor.

but looks like you didn't restart the MC service.
Could you please repeat this but with the following corrections:
1. Stop nworksMC service
2. Delete the "maindb.xml" file (default location: "C:\Documents and Settings\All Users\Application Data\nworks\Management Center")
3. Start nworksMC service. Verify that you don't have any targets in the Connected Servers
4. Re-add the servers you would like to monitor.

If it doesn't help, please open the support case and attach logs of the Management Center.

Thank you,
Irina
Irina Simkina
Enthusiast
 
Posts: 51
Liked: never
Joined: Tue Apr 20, 2010 9:00 am
Full Name: Irina Simkina

Re: Veeam SPI 5.x license issue?

Veeam Logoby apavil » Fri Feb 25, 2011 11:36 am

Thank you it worked perfectly.
apavil
Novice
 
Posts: 4
Liked: never
Joined: Fri Feb 25, 2011 9:41 am
Full Name: Antonin PAVIL


Return to Veeam Smart Plug-in for HP Operations Manager



Who is online

Users browsing this forum: No registered users and 1 guest