{"id":925,"date":"2012-10-30T22:23:47","date_gmt":"2012-10-30T21:23:47","guid":{"rendered":"http:\/\/www.bussink.ch\/?p=925"},"modified":"2018-05-23T18:00:45","modified_gmt":"2018-05-23T16:00:45","slug":"some-vcenter-operations-manager-5-x-tweaks","status":"publish","type":"post","link":"https:\/\/www.bussink.ch\/?p=925","title":{"rendered":"Some vCenter Operations Manager 5.x tweaks"},"content":{"rendered":"<p><strong>Web Interface Timeout Issues<\/strong><\/p>\n<p>I often use the Web Interface of vCenter Operations Manager to check the infrastructure. Because while the client module exist for the vSphere Client, I don&#8217;t find it as optimized in the display and the pane jumping. One of the smaller annoying parts of using vC Ops via the Web Interface is the quick timeout of the user authentication. This can been tweaked by making a small change on the User Interface virtual machine.<\/p>\n<p>Simply edit the\u00a0<strong><code class=\"preserve-code-formatting\">\/usr\/lib\/vmware-vcops\/tomcat\/webapps\/vcops-vsphere\/WEB-INF\/web.xml<\/code><\/strong>\u00a0 file, near the top you will find the following section<\/p>\n<p><span style=\"font-size: small;\"><span style=\"font-size: small;\">&lt;session-config&gt;<\/span><br \/>\n&lt;session-timeout&gt;<em>value<\/em>&lt;\/session-timeout&gt;<br \/>\n&lt;\/session-config&gt;<\/span><\/p>\n<p>You can increase the time to 60, 90 or 120 minutes or set the time to infinite with a &#8216;-1&#8217; value.<\/p>\n<p>Once modified, just restart the vCenter Operations Manager Admin interface with the command<\/p>\n<p><strong><code class=\"preserve-code-formatting\">vcops-admin restart<\/code><\/strong><\/p>\n<p>This is referenced in the <a title=\"VMware KB kb.vmware.com\/kb\/2015135\" href=\"http:\/\/kb.vmware.com\/kb\/2015135\" target=\"_blank\">VMware KB Article 2015135<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<p><strong>\u00a0Log Files Location<\/strong><\/p>\n<p>With the release of vCenter Operations Manager 5.0. and later, the log files have been moved to their own partition, so that if there are lots of logs, they do not file the system partition of the two virtual machines in the vApp.<\/p>\n<p>The logs have been moved to \/data\/vcops\/logs<\/p>\n<div>\n<ul>\n<li><span style=\"font-size: small;\">catalina-web.log<\/span><\/li>\n<li><span style=\"font-size: small;\">localhost-web.log<\/span><\/li>\n<li><span style=\"font-size: small;\">manager-web.log<\/span><\/li>\n<li><span style=\"font-size: small;\">host-manager-web.log<\/span><\/li>\n<\/ul>\n<p>This is referenced in the <a title=\"VMware KB 2032786\" href=\"http:\/\/kb.vmware.com\/kb\/2032786\" target=\"_blank\">VMware KB Article 2032786<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<p><strong>Adding Storage for vCenter Operations Manager<\/strong><\/p>\n<p>Things have changed a lot since the first version of the vCenter Operations Manager 1.0. The data stored on both virtual machine that forms the vApp is now using the <strong>Logical Volume Manager<\/strong>, so adding more space to the Analytics VM or the User Interface VM, is very easy. Simply add a new Disk (Thick Provision Eager Zeroed for performance) to the virtual machines. On restart the new disk will be added the the data_vg (data volume group).<\/p>\n<p>Let&#8217;s just check the Analytics VM before adding a new disk<br \/>\n<pre><code class=\"preserve-code-formatting\">\nlocalhost:~ # &lt;strong&gt;lvdisplay&lt;\/strong&gt;\n--- Logical volume ---\nLV Name \/dev\/data_vg\/data\nVG Name data_vg\nLV UUID aTXaIF-ZhHn-uUhg-0F6o-qHjy-9sI8-Q0QmlN\nLV Write Access read\/write\nLV Status available\n# open 1\nLV Size 400.00 GB\nCurrent LE 102399\nSegments 1\nAllocation inherit\nRead ahead sectors auto\n- currently set to 1024\nBlock device 253:0<\/code><\/pre><\/p>\n<p>localhost:~ # <strong>lvs<\/strong><br \/>\nLV VG Attr LSize Origin Snap% Move Log Copy% Convert<br \/>\ndata data_vg -wi-ao 400.00G<\/p>\n<p>localhost:\/data # <strong>df -k<\/strong><br \/>\nFilesystem\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1K-blocks\u00a0\u00a0\u00a0\u00a0\u00a0 Used Available Use% Mounted on<br \/>\n\/dev\/sda3\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 8111996\u00a0\u00a0 2177068\u00a0\u00a0 5522864\u00a0 29% \/<br \/>\nudev\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 3580976\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 100\u00a0\u00a0 3580876\u00a0\u00a0 1% \/dev<br \/>\ntmpfs\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 3580976\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0 3580976\u00a0\u00a0 0% \/dev\/shm<br \/>\n\/dev\/sda1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 132206\u00a0\u00a0\u00a0\u00a0 18149\u00a0\u00a0\u00a0 107231\u00a0 15% \/boot<br \/>\n\/dev\/mapper\/data_vg-data<br \/>\n412845232 100011536 291862384\u00a0 26% \/data<\/p>\n<p>When I power-down the Analytics VM, I added a 16GB hard disk to the VM, after restart we clearly see the new size.<\/p>\n<p><pre><code class=\"preserve-code-formatting\">\nlocalhost:~ # &lt;strong&gt;lvdisplay&lt;\/strong&gt;\n--- Logical volume ---\nLV Name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/dev\/data_vg\/data\nVG Name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 data_vg\nLV UUID\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 aTXaIF-ZhHn-uUhg-0F6o-qHjy-9sI8-Q0QmlN\nLV Write Access\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 read\/write\nLV Status\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 available\n# open\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1\nLV Size\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 415.99 GB\nCurrent LE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 106494\nSegments\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2\nAllocation\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 inherit\nRead ahead sectors\u00a0\u00a0\u00a0\u00a0 auto\n- currently set to\u00a0\u00a0\u00a0\u00a0 1024\nBlock device\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 253:0<\/code><\/pre><\/p>\n<p>localhost:~ # <strong>lvs<\/strong><br \/>\nLV\u00a0\u00a0 VG\u00a0\u00a0\u00a0\u00a0\u00a0 Attr\u00a0\u00a0 LSize\u00a0\u00a0 Origin Snap%\u00a0 Move Log Copy%\u00a0 Convert<br \/>\ndata data_vg -wi-ao 415.99G<\/p>\n<p>localhost:~ # <strong>df -k<\/strong><br \/>\nFilesystem 1K-blocks Used Available Use% Mounted on<br \/>\n\/dev\/sda3 8111996 2177952 5521980 29% \/<br \/>\nudev 3580976 104 3580872 1% \/dev<br \/>\ntmpfs 3580976 0 3580976 0% \/dev\/shm<br \/>\n\/dev\/sda1 132206 18149 107231 15% \/boot<br \/>\n\/dev\/mapper\/data_vg-data<br \/>\n429355112 100014632 307530516 25% \/data<\/p>\n<p>This is referenced in the <a title=\"VMware KB 2016022\" href=\"http:\/\/kb.vmware.com\/kb\/2016022\" target=\"_blank\">VMware KB Article 2016022<\/a>.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Web Interface Timeout Issues I often use the Web Interface of vCenter Operations Manager to check the infrastructure. Because while the client module exist for the vSphere Client, I don&#8217;t find it as optimized in the display and the pane jumping. One of the smaller annoying parts of using vC Ops via the Web Interface [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":989,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[9],"tags":[43,42],"_links":{"self":[{"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/posts\/925"}],"collection":[{"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=925"}],"version-history":[{"count":22,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/posts\/925\/revisions"}],"predecessor-version":[{"id":947,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/posts\/925\/revisions\/947"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/media\/989"}],"wp:attachment":[{"href":"https:\/\/www.bussink.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=925"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=925"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=925"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}