<?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>Call-Home on BAFM</title><link>https://christian.blog.pakiheim.de/tags/call-home/</link><description>Recent content in Call-Home on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Sat, 22 Nov 2008 17:31:50 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/call-home/index.xml" rel="self" type="application/rss+xml"/><item><title>IBM TS7530 and DNS</title><link>https://christian.blog.pakiheim.de/posts/2008-11-22_ibm-ts7530-and-dns/</link><pubDate>Sat, 22 Nov 2008 17:31:50 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=1263</guid><description>&lt;p&gt;Well, we had our TS7530 delivered in late September, the day after the IBM service guys came by to prep the VTL for our needs (IBM sells the thing as black box). Now, since that day; they fought with the Call Home functionality. The trouble was simply, that the Call Home Service running on the Virtualization Engines just didn&amp;rsquo;t start.&lt;/p&gt;
&lt;p&gt;After about 6 weeks of trial and error (and the IBM service guys popping in every second week), they finally found the cause of the Call Home Service not being able to start. Domain Name Resolution. Neither the IP addresses of the VE&amp;rsquo;s nor the VE console were registered in our DNS/or local host files.&lt;/p&gt;</description></item></channel></rss>