Insight journal for vCenter

Similar Questions

• Overview journal and vCenter Heartbeat

  What are the implications of the use of Log insight with vCenter Heartbeat?  If vCenter server heartbeat Eve, insight Journal will continue to operate without interruption or loss of newspapers as the failover takes place?

  Are there special configurations specific to the use of Log Insight with heartbeat?

  The vCenter Heartbeat is to keep a backup of vCenter server available at all times. This is achieved through a mechanism of steps that ensures that everything that happens on the primary instance of vCenter server is also on the secondary server instance, vCenter. Given that the configurations of the server vCenter instances are guaranteed the same, newspaper Insight would not be able to tell the difference.

  However, vCenter heartbeat supports three types of configuration: LAN, stretched LAN and WAN. For LAN and LAN stretched assets vCenter Server's IP address is moved during failover. For WAN, during a failover Exchange IP address of the instance of vCenter server, but pulse warns DNS change. Because with LAN and LAN stretched the IP address of the instance of vCenter server remains the same, newspaper Insight will continue to work as expected once the recovery has taken place and the new primary instance of vCenter server sent a free ARP. In the WAN configuration, the IP address of vCenter Server changes. If you have configured Log Insight to connect to the instance of vCenter Server by IP address then after failover Log Insight will not be able to collect information from the new vCenter server IP address. In this case, you must change the configuration of log Insight and the new IP address would be considered a completely separate vCenter server instance. If you have configured Log Insight to connect to the instance of vCenter by FULL domain name server then Insight journal will pick up the change on the next polling interval. If you end up in a State where Log Insight is no longer perceives the information from one instance of vCenter server, once the issue has been addressed, Insight Journal will collect information all gaps between where he was and where it was fixed. In short, Insight journal keeps track of the latest information collected from one instance of vCenter server and can collect the missing information.

  In short, Journal Insight should work with vCenter Heartbeat even if it only is not officially supported at this time (by the interoperability matrix). If you use vCenter Heartbeat in a WAN configuration, then you must enable vSphere integration with a FULL domain name for the vote will continue to operate after the failover. I hope this helps!

• NetApp Insight Journal content packs

  Guys,

  I installed the insight journal, and my virtual centres taking data and install vcops. I installed the content to netapp pack, but it doesn't seem to be bringing in my controllers of netapp data. Y at - there a step I'm missing or additional configuration?

  Thank you

  Ryan

  The content of NetApp pack requires ONTAP cluster. If you don't see any data being filled, then I assume that you are running the legacy version. If you want that NetApp to build a content for legacy mode pack then leave a comment on the content of NetApp pack to the Exchange Solution.

• Minimum privileges for vCenter/vCOPS access?

  Is there a documentation on the minimum privileges required for newspaper Insight to access vCenter and vCOPS? The security guide do not detail this.

  Thank you.

  vCenter Server = read only privileges (the user must be set to the object of vCenter Server root and have the box spread selected)

  vCenter Operations Manager is the user's privileges.

  The Security Guide is here, but does not contain this information: Security Log Insight 1.0 Beta Guide

• Problem with OpenManage integration for vCenter - OMSA status: update required

  Hello

  We have a problem with the configuration of OpenManage integration on a vSphere 5.5 U2 Cluster. We have deployed IMO for vCenter v 2.3.0 build 290 aircraft, and we have installed manually OMSA VIB v7.4.0.2 on our 5.5. U2 ESXi hosts.

  The question we face is respect for vSphere host - when we start the Wizard "Fix Non compliant vSphere Host" it displays the correct version of the OMSA - 7.4.0.2 but OMSA status is "required update".

  Whe test us the connection to hosts using "Test the connection profile", it hangs at 0% and will be never finished.

  Also in the OpenManage integration in vSphere Client "Frimware" tab option is grayed out.

  Please indicate how we can make this work?

  Concerning

  Milan

  Well, I did some research more and found that ESXI 5.5 U1 and U2 don't are not supported by OMSA right now.

  FTP://FTP.Dell.com/manuals/all-products/esuprt_software/esuprt_virt_solutions/Dell-Mgmt-plugin-for-VMware-Center-2.3_Release%20Notes_en-us.PDF

  ESXi 5.5 U1 and U2 are supported only for the OMIVV on the servers of 12th and 13th generation who are capable of out-of-band management and require no OMSA must be installed on the host system. We intend to add a supported of the OMSA version at a later date.

  Thank you

• How to change the MOB OpenManage integration for vCenter Server registration

  A few months back, I've updated our installation of the vCenter for v2 plugin, now called OpenManage integration for vCenter Server. When you perform the upgrade, we have kept the old base done vs a new installation. During the upgrade process, we deployed the new device under a new name of the computer.

  Everything works well except that we noticed an annoying thing. Registration of the plugin is the former name of the server instead of the name of the new server-oriented. It is validated by looking at the web page MOB: http://vcenter Server/fmt drilling then down through:

  Content--> Extension Manager--> extensionList ["com.dell.plugin.OpenManage_Integration_for_VMware_vCenter"] --> server--> URL string

  The configuration of the appliamnce shows the correct new name of the device and the administration console is accessible via the new name for the device. The only place where we see the old name of the device is in the MOB config.

  We tried to remove the plugin and added, but still cannot change the value of server URL to reflect the new name of the device. Until we solve this problem, I work around the problem by keeping just the DNS entry for the old name of the server in DNS.

  Anyone know who to change the property MOB for the URL of the server?

  I solved the problem.

  I found the following article that shows how to upgrade the extension. I just cut and paste into my current values with the URL of update and now all is good.

  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2060127&sliceId=1&docTypeID=DT_KB_1_1&dialogID=236869583&StateID=0%200%20236885165

• How to allocate disk space for vCenter server logs

  Hello

  I plan to level 4.1 to 5.5 U2d vCenter on the customer site. One of the conditions set out in the vSphere upgrade guide is:

  "In vCenter Server 5.x, the default size for vCenter Server connects is larger than in vCenter Server 4.x. make sure that the disk space allocated for the log folder is sufficient for this increase 450MB."

  My question is how to allocate disk space for the log file and where can I find the disk space allotted to file papers to vCenter 4.1 existing?

  Just see the free space on the partition where the vCenter server logs are stored. If it is insufficient, increase the size of the virtual disk and then increase the file system to the guest OS.

• SQL Server edition full for vCenter Server 6.0

  Hello

  Just learn that vCenter 6.0 does not support SQL Server Express.

  We intend to use SQL Server 2008R2 as the database of vCenter Server 6.

  We would like to ask for your opinion if we should use the full 32-bit or 64-bit SQL Server Edition?  For SQL Server Express, 64 - Bit is used, I think that we need to use 64 bits one, is this correct?

  Your opinion is requested.

  Just learn that vCenter 6.0 does not support SQL Server Express.

  The Windows 6.0 vCenter dropped the integrated SQL Express, BUT instead, it comes with a SQL database vPostgres shipped to replace it with similar restrictions. You don't need to install your own SQL server if you're ok with these limits. See the following article:

  vSphere 6 - clarify misinformation. VMware vSphere Blog - VMware Blogs

  Databases are supported for installing windows SQL 2008 R2, 2012 and 2014, Oracle 11g and 12 c as well as the possibility of using an embedded database vPostgres on windows vPostgres is limited to 20 guests and 200 VMs. Upgrades where SQL express is installed will be converted to vPostgres. The vCenter Server Appliance supports the vPostgres shipped to full scale, the host of 1000 and 10,000 virtual computers and is the database recommended for vCenter server unit. Oracle 11g and c 12 external databases are also supported for this version, look for these to drop in the future releases.

  It is also possible to keep an existing SQL Express DB when you perform an upgrade:

  VMware KB: Upgrade vCenter Server 6.0 without migration of the SQL database to vPostgres

  If you use your own SQL server to go with a 64-bit version and stick them on products VMware interoperability Matrices.

• Cannot find a service record for vCenter service with the host name "IP address"

  After upgrading to vCenter native 5.5 to vSphere Client device everything works, but not all orders for PowerCLI.

  After a command gives me error under VMware vSphere PowerCLI 6.0 Release 1

  Get-TagCategory: 13.07.2015 16:50:48 Get-TagCategory could not find a service record for vCenter service with host name 10.x.x.x

  In Zeile:2 Zeichen:1

  + Get-TagCategory

  + ~~~~~~~~~~~~~~~

  + CategoryInfo: ObjectNotFound: (:)) [Get-TagCategory], VimException)

  + FullyQualifiedErrorId: ViCore_InventoryServiceProxy_GetInventoryServiceInfo_NoVcRegistration, VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTagCategory

  does anyone have a solution or an idea for this problem?

  Best

  Marco

  I have exactly the same problem. Are there solutions yet?

  Best regards

  René

  Found the solution in the database (2127028).

• I would like to download the license for Vcenter 5.5

  Hello:

  We recently purchased a new (HP DL380 Gen9) ESXi host and that host will work with Version 5.5 Update 2.  I was asked my our VMware consultant to connect to our VMware account and get the license for Vcenter 5.5 .  I can log on to the account; but, how to the license for Vcenter 5.5?

  Then the license "vCenter Server 5 Essentials" should be sufficient. You should be able to download vCenter 5.5 from here (but don't forget to take the update correct level: 5.5, 5.5 U1 or U2 5.5): VMware vSphere 5: Private Cloud Computing, server and data center virtualization

  And you should think about upgrading 5.1 hosts after that vCenter device is installed and configured.

• Setting up Certification Authority (CA) signed certificates for vCenter Server Appliance 6

  Hi all

  Recently, I managed to migrate to vCenter Server Appliance 6. 5.5, there was a large KB (2057223) on Configuring Certificate Authority (CA) signed certificates for vCenter Server Appliance. I tried to do as it says configure the certificate for v6.

  Unfortunately, I understand that some services such as lighttpd are changed in version.

  Can anyone provide a new instruction for the v6?

  Thank you

  Thank you. That helped me to see the idea. However, the explanation in the pages that was not complete. I had to search for more.

  This blog helped me solve my problem with the generated certificate:

  http://longwhiteclouds.com/2015/03/22/vSphere-6-using-Vmca-as-a-subordinate-CA/

• Get the number of vCPU (hearts by shocket) for vCenter VM

  Hello..

  I'm changing vCPU number scale using a script. I succeeded when the number of cores by shocket is 1, but this does not work if the number of cores, it's more than one, so I want to check the number of cores per VM shocket.

  Please help me get number of vCPU (hearts by shocket) for vCenter VM. Answer as soon as possible it's urgent...

  Thank you!!

  Looking for: vm.config.hardware.numCoresPerSocket where vm is an VC:VirtualMachine object.

  Your total number of cores would be (numCoresPerSocket x numCPU)

  Check this for some more tips: numCoresPerSocket

• Management Pack for vCenter Hyperic 5.8, where?

  Hi guys.

  Do you know where to find the management to vCenter Hyperic 5.8 Pack?

  I vCloud Suite 5 Enterprise and I installed vCops 5.8 and vFabric Hyperic 5.8, but I can't find the Management Pack for vCenter Hyperic 5.8.

  The Exchange Vmware Solutions site offers only 5.7 release for download

  Greetings.

  You will find this VMware VMware Solution Exchange Management Pack: https://solutionexchange.vmware.com/

• What happens IF we replace the default certificates for vCenter 5.1?

  Does anyone have specific vmware documents indicating what happens IF we replace the default certificates for vCenter 5.1 SSO, inventory, Web Client etc... services?

  I found this below at page 19 of https://www.vmware.com/files/pdf/products/vCenter/VMware-vCenter-Server-Single-Sign-On.pdf

  Certificates update

  When you install the vCenter Single Sign-On, each component that registers with it - including

  vCenter Single Sign-On himself - uses SSL to communicate between components and saved solutions.

  By default, SSL certificates are generated automatically by VMware installation and upgrade process

  and are sufficient for the operational security for most VMware customers.

  Some clients prefer to use their own self-signed or purchased SSL certificates. A tool has been developed to

  help the insertion of these certificates after vCenter Server installation. Because of the additional knowledge

  required to create and install self-signed certificates, we recommend that you review the following knowledge of VMware

  basis of articles:

  "Deployment and using the tool to automate SSL certificate.

  (VMware 2041600 knowledge base article)

  "Generation of certificates for use with the VMware Certificate SSL automation tool"

  (VMware 2044696 knowledge base article)

  In 10 years your vCenter starts (because of expiry of the certificate).

  Your users will see pesky warnings of SSL certificate when connecting components.

  Apart from that all traffic is always secure and encrypted with certificates by default, you have simply a chain of trust for them.

• Requirements of ports for vCenter Server 5.1 - SysLog Collector

  Hi all

  Has anyone installed a SysLog collector?

  My book of vmware by Lowe mentions little on the ports for it.

  During the installation of the server, he gave me a list of ports.

  I accepted all the flaws, except that I changed the ports http to 81 and 8081 because IIS is installed (vmware docs say to use one port other than 80, if IIS is already installed)

  Now, during the installation of the SysLog collector it asks which http port I use.

  The vmware docs nothing mentioned on the syslog http port is my book. The vmware for TCP docs show that.

  ESXi Syslog Collector

  8001

  TCP

  ESXi

  vCenter Server

  Network syslog server

  Just use port 81 as the http port I have set up for vcenter server? The web interface won't connect through this port? There will be a conflict?

  I used netstat and port 82 is not used. Should I use?

  The other settings works ok?

  There is no firewall involved; vCenter server and the VMs system will reside on the same site

  Thanks in advance

  port 81, that is according to the third screenshot! 8081 is for Tomcat!