<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Svc on BAFM</title><link>https://christian.blog.pakiheim.de/tags/svc/</link><description>Recent content in Svc on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Fri, 08 Aug 2014 08:28:32 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/svc/index.xml" rel="self" type="application/rss+xml"/><item><title>IBM SVC: Copy VDisk Host-Mapping from one host to another</title><link>https://christian.blog.pakiheim.de/posts/2014-08-08_ibm-svc-copy-vdisk-host-mapping-from-one-host-to-another/</link><pubDate>Fri, 08 Aug 2014 08:28:32 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2591</guid><description>&lt;p&gt;As I wrote &lt;a href="https://christian.blog.pakiheim.de/posts/2014-08-08_loooong-time" title="Loooong time"&gt;a few days ago&lt;/a&gt;, I started a new job. One of my first (voluntary) tasks was writing a shell script which would copy a VDisk Host-Mapping from a given host to another. This is useful, if you do have a lot of ESX servers for example and a few roaming ones.&lt;/p&gt;
&lt;p&gt;Now, if say, you need to do some ESX-Updates and you would like to add the roaming one to a given farm, you would be in a dark an deary place. You would be required to either click through the GUI a dozen times (in my case, it might have needed ~200 clicks) or type svcinfo lshostvdiskmap &lt;!-- raw HTML omitted --&gt; and svctask mkhostvdiskmap &lt;!-- raw HTML omitted --&gt; -force (these are incomplete command references) a few times.&lt;/p&gt;</description></item><item><title>SVC: Find WWPN</title><link>https://christian.blog.pakiheim.de/posts/2010-11-15_svc-find-wwpn/</link><pubDate>Mon, 15 Nov 2010 17:50:56 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=3621</guid><description>&lt;p&gt;Today we had (once again) hardware troubles. We ended up replacing a lot of things, but in the end it was a) the HBA and b) apparently some memory DIMMs. Now, that isn&amp;rsquo;t SVC related. However, we built in another HBA (from our Standby hardware), which apparently already had been assigned to a host.&lt;/p&gt;
&lt;p&gt;Now, since you can&amp;rsquo;t search for a WWPN (at least not that I know of), I ended up writing a little script (yup, &lt;strong&gt;AGAIN&lt;/strong&gt;) in order to do that for me!&lt;/p&gt;</description></item><item><title>SVC: Migrate VDisks off a MDisk Group onto another</title><link>https://christian.blog.pakiheim.de/posts/2009-10-29_svc-migrate-vdisks-off-a-mdisk-group-onto-another/</link><pubDate>Thu, 29 Oct 2009 18:09:17 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2739</guid><description>&lt;p&gt;Out of necessity, another SVC shell script was just born. If you ever need to migrate a whole MDisk group onto another, you quickly discover the limited application of the SVC GUI. Now, you could query the VDisks using your original MDisk Group and then copy and paste the VDisk&amp;rsquo;s name (or the VDisk ID) into a command line and simply reuse that svctask migratevdisk command over and over.&lt;/p&gt;
&lt;p&gt;Luckily IBM blessed the SVC with an SSH interface. So again, we can write a (kinda) simple shell script which may look like this:&lt;/p&gt;</description></item></channel></rss>