tag:blogger.com,1999:blog-13748074884864225552024-03-04T22:15:16.162-08:00Virtualization & StorageAnonymoushttp://www.blogger.com/profile/02129302443328310732noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-1374807488486422555.post-86499530088365049292018-10-26T02:27:00.000-07:002018-10-26T02:27:31.855-07:00VSAN - Políticas de almacenamiento. Demostración en video.<div dir="ltr" style="text-align: left;" trbidi="on">
<br />
<br />
<br />
<br />
En este video podemos ver como utilizar las políticas de almacenamiento en VSAN de forma dinámica y cambiar el almacenamiento de la VM sin apagarla.<br />
<br />
Podemos ver el tiempo que necesita para arrancar la VM, como creamos después una política que limita las IOPSy la VM tiene una respuesta mucho más lenta al arrancar y finalmente como al cambiar de nuevo la política con la VM en marcha vuelve a tner buen rendimiento.<br />
<br />
<br />
<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<iframe allowfullscreen='allowfullscreen' webkitallowfullscreen='webkitallowfullscreen' mozallowfullscreen='mozallowfullscreen' width='320' height='266' src='https://www.blogger.com/video.g?token=AD6v5dz86P6f0y7LybE-fXWJOuTVrGzIgKl8JtDrqqFMAoD3logafENaneNqNGQTnnCBPiHn3gzfuoa64sLbg8Nk0A' class='b-hbp-video b-uploaded' frameborder='0'></iframe></div>
<br />
<br />
<br />
<a href="https://www.linkedin.com/in/raul-de-la-flor-valls-904a6448/">
<img border="0" src="http://www.linkedin.com/img/webpromo/btn_myprofile_160x33.png" id="linkedinImg" /></a></div>
Anonymoushttp://www.blogger.com/profile/02129302443328310732noreply@blogger.com0tag:blogger.com,1999:blog-1374807488486422555.post-77990115516558254112013-11-29T03:29:00.005-08:002013-11-29T03:29:41.345-08:00EMC VNX 5200 VIA initialization fails writing sysadmin password<div dir="ltr" style="text-align: left;" trbidi="on">
We just initialized a new VNX 5200 and after finishing we couldn't log in with the new sysadmin password we choose. However we could log as root and nasadmin.<br />
<br />
So we created a new global user called temp from ssh connection to the CS and accessed unisphere with the new user and changed sysadmin password.<br />
<br />
Below you can see the command we used:<br />
<br />
<b><i>navicli -h spa security -adduser -user temp -password temp -scope 0 -role administrator</i></b><br />
<br />
Finally we could enter Unisphere with sysadmin and finish the installation.</div>
Anonymoushttp://www.blogger.com/profile/02129302443328310732noreply@blogger.com0tag:blogger.com,1999:blog-1374807488486422555.post-14221745997994177212013-09-26T23:42:00.001-07:002013-09-26T23:42:02.980-07:00Error installing Exchange 2013 CU2 on Exchange 2007 organization<div dir="ltr" style="text-align: left;" trbidi="on">
Yesterday I installed for first time a new Exchange 2013 on a company with Exchange 2007. We have installed some new 2013 Exchange but this was the first migration.<br />
<br />
After accomplish all prerequisites on Microsoft guides we started to install and it ended on error.<br />
<br />
The error was "length of the property is too long the maximum length is 64" and it was close to a line referring to Offline Address Book.<br />
<br />
In Spanish the OAB was named "Libreta de direcciones sin conexión de exchange".<br />
<br />
I googled a little and couldn't find any reference to this error and finally just tried something.<br />
<br />
I just renamed the OAB to "OAB" and tried again to install.<br />
<br />
This time installation finished OK!!!<br />
<br />
<br /></div>
Anonymoushttp://www.blogger.com/profile/02129302443328310732noreply@blogger.com0tag:blogger.com,1999:blog-1374807488486422555.post-40910776475366524632013-07-01T04:10:00.000-07:002013-07-01T04:15:48.376-07:00EMC File Replication VNX to VNXeRecently we needed to configure File replication from a VNX array to a VNXe.<br />
I searched EMC support and communities and it was a surprise that there was no documentation or guide.<br />
<br />
I have to look for the compatibility matrix again to see if it was possible.<br />
<br />
<a href="https://elabnavigator.emc.com/vault/pdf/EMC_VNXe_ESSM.pdf">https://elabnavigator.emc.com/vault/pdf/EMC_VNXe_ESSM.pdf</a><br />
<br />
Then I tried to do the inverse one, VNXe to VNX as I had a manual.<br />
<br />
<a href="https://www.ndm.net/emcvnx/pdf/vnx/h8270-replicating-vnxe-cifs-nfs-shared-folders-vnx.pdf">https://www.ndm.net/emcvnx/pdf/vnx/h8270-replicating-vnxe-cifs-nfs-shared-folders-vnx.pdf</a><br />
<br />
At first time I had a problem establishing the trust and finally it result I needed to add a route at DataMover level on the VNX since the two arrays are in different subnets.<br />
<br />
Once I got this solved I followed instructions and it worked fine. Also I tried to make a switch-over on replication and also worked.<br />
<br />
Now I created a Replication Destination on Shared Folders screen of the VNXe. The wizard asked which one was the origin and created a Shared folder mounted as only read and with the right size and protection size.<br />
<br />
When I tried to set a new replication from VNX as I entered the VNXe as destination the Unisphere screen failed.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj34Vj-1isARFQH8jpD81sUJN5b89S4wd_1yOCBaUrWBX-Xi76GBZYqbla4HQ17kBJhpgKIec73jtUIhIV-XEhavHIfJvmTeaLw9-FiFHDNkjk119iEJY2FGLz6K8xp0y8FHeADr0XMODk/s869/screnshot1.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="445" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj34Vj-1isARFQH8jpD81sUJN5b89S4wd_1yOCBaUrWBX-Xi76GBZYqbla4HQ17kBJhpgKIec73jtUIhIV-XEhavHIfJvmTeaLw9-FiFHDNkjk119iEJY2FGLz6K8xp0y8FHeADr0XMODk/s869/screnshot1.jpg" width="640" /></a></div>
<span style="font-family: "Calibri","sans-serif"; font-size: 11.0pt; mso-ansi-language: ES; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-fareast-font-family: Calibri; mso-fareast-language: ES; mso-fareast-theme-font: minor-latin;"><br /><!--[endif]--></span>
<span style="font-family: "Calibri","sans-serif"; font-size: 11.0pt; mso-ansi-language: ES; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-fareast-font-family: Calibri; mso-fareast-language: ES; mso-fareast-theme-font: minor-latin;">I then tried to look for info about doing it on commands from Control Station and I found a blog where some one had the same problem. Thanks to Jon Austin by the way.</span><br />
<span style="font-family: "Calibri","sans-serif"; font-size: 11.0pt; mso-ansi-language: ES; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-fareast-font-family: Calibri; mso-fareast-language: ES; mso-fareast-theme-font: minor-latin;"><br /></span>
<a href="http://www.integrateddatastorage.com/blog/2011/11/04/fun-with-darts/">http://www.integrateddatastorage.com/blog/2011/11/04/fun-with-darts/</a><br />
<br />
The main problem was how to know the destination FS ID on the vnxe system.<br />
<br />
So I connected to ssh on both arrays.<br />
<br />
On vnxe I logged as service and entered the service password which was the same that admin one.<br />
I executed <i><span style="color: blue;">svc_service_shell </span></i>so I could use commands on the VNXe.<br />
I don't know the password for that since some one form support put it the day before for other thing and there is a time when it expires. It looks like it takes a couple of days until it expires.<br />
<br />
Then I executed<i><span style="color: blue;"> /nas/bin/nas_fs -list</span></i> so I could see the ID for the replication FS.<br />
<br />
After I logged on VNX CS with ssh as nasadmin user<br />
<br />
I executed <span style="color: blue; font-style: italic;"> nas_cel -interconnect -list </span>so I could see the interconnect id (VNXe SPA) where the destination FS was published.<br />
<br />
and finally executed this command and finally got replication started!!!<br />
<br />
<span style="color: blue;"><i> nas_replicate -create FS_Name -source -fs id=13 -destination -fs id=42 -interconnect id=20004 -source_interface ip=x.x.x.x -destination_interface ip=x.x.x.x -max_time_out_of_sync 10 -overwrite</i></span><br />
<br />
Overwrite option was needed because it fails other way.<br />
<br />
That was all, after 20 hours file system is replicated and working fine.<br />
<br />
<br />
<div>
<br /></div>
<br />Anonymoushttp://www.blogger.com/profile/02129302443328310732noreply@blogger.com0tag:blogger.com,1999:blog-1374807488486422555.post-3045143222177172682012-10-15T03:13:00.000-07:002012-10-15T03:13:36.823-07:00Error 3221684229 Installing Exchange 2007 (Mailbox Role) - On Windows Server 2008 R2 and OWA not working<div dir="ltr" style="text-align: left;" trbidi="on">
Hi,<br />
<br />
this post is composed by a couple of issues that can appear when migrating exchange 2003 to 2007.<br />
Since Exchange 2007 is an old software if you install it today on a Windows 2008 R2 Server you can get this error: Error 3221684229 Installing Exchange 2007 Mailbox Role.<br />
<br />
I found this post that helped me out.<br />
<br />
<a href="http://www.petenetlive.com/KB/Article/0000262.htm">http://www.petenetlive.com/KB/Article/0000262.htm</a><br />
<br />
Solution as easy as running the installer on Vista compatibility mode.<br />
<br />
This generated next problem, it was a typical install and all roles where installed except the mailbox.<br />
After changing compatibility mode I added Mailbox Role.<br />
<br />
Then we starting trying the server and OWA web page appeared but it didn't authenticate.<br />
Finally I found two posts that help me out:<br />
<br />
<a href="http://exchangeserverpro.com/modifying-exchange-server-2007-roles-breaks-outlook-web-access#comment-10670">http://exchangeserverpro.com/modifying-exchange-server-2007-roles-breaks-outlook-web-access</a><br />
<br />
<a href="http://itproafrica.com/technology/exchange/owa-broken-on-exchange-2007-on-windows-2008-red-x-appear-instead-of-web-pages/">http://itproafrica.com/technology/exchange/owa-broken-on-exchange-2007-on-windows-2008-red-x-appear-instead-of-web-pages/</a><br />
<br />
We needed to install Exchange SP3 and review IIS prerequisites.<br />
<br />
<br /></div>
Anonymoushttp://www.blogger.com/profile/02129302443328310732noreply@blogger.com0tag:blogger.com,1999:blog-1374807488486422555.post-52512830468950007762012-07-30T23:57:00.001-07:002012-07-30T23:57:04.305-07:00VMWARE VIEW Problem cloning master image for linked clones on v5.1<div dir="ltr" style="text-align: left;" trbidi="on">
On a small new installation of Vmware View 5.1 we had problems when creating linked clone pools.<br />
It is a lab install on SATA disk and cloning takes about 70 minutes.<br />
It always finished with an error "Connection Server - View Composer Fault: VC operation exceeded the task
timeout limit of 0 mins set by the View Composer for <VM
instance>"<br />
So after googling a lite bit I founf some post on Vmware communities that solved the problem.<br />
<br />
<a href="http://communities.vmware.com/message/2063937">http://communities.vmware.com/message/2063937</a><br />
<br />
Thanks to hettefagh I could solve my problem.<br />
<br />
Here you can read the solution:<br />
<br />
<br />
1. Stopped the View Composer service.<br />
<div style="height: 8pt; min-height: 8pt; padding: 0px;">
<br /></div>
2.
Made a backup copy of C:\Program Files (x86)\VMware\VMware View Composer\SviWebService.exe.config and saved in the same folder.<br />
<div style="height: 8pt; min-height: 8pt; padding: 0px;">
<br /></div>
3. Edited the SviWebService.exe.config and changed the line<br />
<div style="height: 8pt; min-height: 8pt; padding: 0px;">
<br /></div>
<VirtualCenter PropertyCollectorTimeout="60" /><br />
<div style="height: 8pt; min-height: 8pt; padding: 0px;">
<br /></div>
to read<br />
<div style="height: 8pt; min-height: 8pt; padding: 0px;">
<br /></div>
<VirtualCenter PropertyCollectorTimeout="60" VcTaskTimeout="90" /><br />
<div style="height: 8pt; min-height: 8pt; padding: 0px;">
<br /></div>
4. Saved the change and restarted Composer. Confirmed the service is running again without error.<br />
</div>Anonymoushttp://www.blogger.com/profile/02129302443328310732noreply@blogger.com0tag:blogger.com,1999:blog-1374807488486422555.post-23552968036276088742012-03-07T08:58:00.000-08:002012-03-07T08:59:25.717-08:00Esxi5 disconnected and responding ping.<div dir="ltr" style="text-align: left;" trbidi="on">
<br />
Recently we have some serious problems on a small project implementation.<br />
<br />
<br />
We had 2 Cisco UCS C200 M2 servers, 2 Cisco MDS9148 and a EMC VNX5100 storage array.<br />
The servers used Qlogic 8GB Fiber channel cards. The problem appeared always on heavy storage use (backup tasks mostly), but it could be once a week.<br />
<br />
When accessing to the esxi console you could write user and password but you could not enter.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjBpfdj3jOiSvaaph82xHdAYFVCHWjgQO9V487uUZBCh3lWGcc0fZKpQmZKTB3HJ5aTw5R9kZTrrKsUeMPwLWAn4-Di36YxQ-wfjvKG4Lp5U7u5HG4xehClilYmtNwCb6e7fDldhf8LIiU/s1600/Captura.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="145" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjBpfdj3jOiSvaaph82xHdAYFVCHWjgQO9V487uUZBCh3lWGcc0fZKpQmZKTB3HJ5aTw5R9kZTrrKsUeMPwLWAn4-Di36YxQ-wfjvKG4Lp5U7u5HG4xehClilYmtNwCb6e7fDldhf8LIiU/s320/Captura.JPG" width="320" /></a></div>
<br />
After that you needed to restart the Esxi and Virtual Machines were down.<br />
<br />
I opened a SR on VMware but solved the problem before they answer.<br />
<br />
After looking at vmkernel.log I searched on Google for info about errors appearing and finally I founded a KB Article that was very interesting:<br />
<br />
<h2>
<a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1030265">vHBAs and other PCI devices may stop responding in ESX/ESXi 4.1 and ESXi 5.0 when using Interrupt Remapping</a></h2>
<div>
<br />
Also I founded at Vmware communities some threads with same case:</div>
<div>
<br /></div>
<div>
<a href="http://communities.vmware.com/message/1983041">http://communities.vmware.com/message/1983041</a> (Cisco servers)</div>
<div>
<br /></div>
<div>
<a href="http://communities.vmware.com/thread/341512">http://communities.vmware.com/thread/341512 </a> (IBM, Supermicro) </div>
<div>
<br /></div>
<div>
We execute the actions in the KB and everything is working fine after 20 days.</div>
<div>
<br /></div>
<div>
<br /></div>
<div>
Hope this helps others on searching solutions!!</div>
</div>Anonymoushttp://www.blogger.com/profile/02129302443328310732noreply@blogger.com0tag:blogger.com,1999:blog-1374807488486422555.post-91526505779710951622012-02-24T00:51:00.002-08:002012-02-24T00:51:46.737-08:00VMWARE Data Recovery Plugin: Error could not connect to the Data Recovery Service on the Appliance<div dir="ltr" style="text-align: left;" trbidi="on">
Some times after installing Data Recovery Plugin you can't connect to the appliance. You get this message: <i>Error could not connect to the Data Recovery Service on the Appliance.</i><br />
The curious thing is that you can't connect from vSphere client installed on VCenter or other desktops.<br />
I found a solution on Vmware communities. You need to rename some dlls and it will work again.<br />
<br />
<br />
<div class="MsoNormal" style="text-indent: 35.4pt;">
<i><span lang="EN-US" style="color: #1f497d; font-family: "Calibri","sans-serif"; font-size: 11.0pt; mso-ansi-language: EN-US;">Renaming C:\Windows\System32\libeay32.dll and
C:\Windows\System32\ ssleay32.dll and rebooting - all works fine.</span></i></div>
<div class="MsoNormal" style="text-indent: 35.4pt;">
<i><span lang="EN-US" style="color: #1f497d; font-family: "Calibri","sans-serif"; font-size: 11.0pt; mso-ansi-language: EN-US;"><br /></span></i></div>
<div class="MsoNormal" style="text-indent: 35.4pt;">
<span lang="EN-US"><span style="color: #1f497d; font-family: Calibri, sans-serif;"><span style="font-size: 11pt;">I found that on this </span><span style="font-size: 15px;">thread</span><span style="font-size: 11pt;">: </span></span></span><a href="http://communities.vmware.com/thread/328337" style="font-family: 'Times New Roman', serif; font-size: 12pt;">http://communities.vmware.com/thread/328337</a>3</div>
<div class="MsoNormal" style="text-indent: 35.4pt;">
<br /></div>
</div>Anonymoushttp://www.blogger.com/profile/02129302443328310732noreply@blogger.com1tag:blogger.com,1999:blog-1374807488486422555.post-62726880883965649132012-02-22T09:06:00.000-08:002012-02-22T09:28:08.855-08:00error mounting replica LUNS on VMWARE ESXi5<div dir="ltr" style="text-align: left;" trbidi="on">
Hi,<br />
<br />
a days ago I had some problems trying to test replicas between two EMC arrays connected to different vSphere 5 clusters.<br />
I openned a request with EMC and they told me replica was fine.<br />
<div class="MsoNormal" style="color: black;">
I tried to mount the datastore by using esxcli the next command: <i><br /></i></div>
<div class="MsoNormal" style="color: black;">
<i>esxcli storage vmfs snapshot mount -u "4xxxxxx-99xxx-b555-001xxxxxx8"</i></div>
<div class="MsoNormal" style="color: black;">
It faulted with error and redirected me to vmkernel.log.</div>
<div class="MsoNormal" style="color: black;">
I reviewed vmkernel.log and I saw an error “Denying reservation access on an ATS-only vol”, I search for this error (and many others).</div>
<div class="MsoNormal" style="color: black;">
Finally I got this KB article on Vmware. It is not really same case but I tried it on a nonproduction server and finally VMFS5 datastore could be mounted.</div>
<div class="MsoNormal">
<a href="http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2006858"><span lang="EN-US">http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2006858</span></a></div>
<br />
After disabling these features I finally could mount snapshots of replica, and the replica itself when testing promote.</div>Anonymoushttp://www.blogger.com/profile/02129302443328310732noreply@blogger.com0