<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: omniback error in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636977#M42632</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt; Most likely causes are 1) DNS / Network hostname resolutions problems - you could check using ping/nslookup or resolve hostnames first using /etc/hosts (files) via /etc/nsswitch.conf and ensure the cell manager and client are listed in here ? or 2) licensing .&lt;BR /&gt;&lt;BR /&gt;ps also check in /etc/opt/omni/cell_server, cell_info etc to make sure hostnames listed tie up with those returned from nslookup ie all entries are fully qualified domain names or short hostnames but not a mix of both it can cause problems.&lt;BR /&gt;&lt;BR /&gt;I'd post this to the openview forums , check the above and add the details to your post.&lt;BR /&gt;&lt;BR /&gt;also look in /vat/opt/omni/logs/* any clues ?&lt;BR /&gt;&lt;BR /&gt;Also of use : run omnicc &amp;gt;text.txt and details of whether this has ever worked, hpux versions or is NT involved, Version of OB II etc .... would be useful too !&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 31 Dec 2001 14:07:35 GMT</pubDate>
    <dc:creator>Alex Glennie</dc:creator>
    <dc:date>2001-12-31T14:07:35Z</dc:date>
    <item>
      <title>omniback error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636975#M42630</link>
      <description>Getting an error of "Cannot access the Cell Manager." while trying to export the jhpux11.00 box as omniback client. I am giving the following command :-&lt;BR /&gt;# ./omnicc -export_host apps2.etcs.com  &lt;BR /&gt;&lt;BR /&gt;Any Clues?&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Dec 2001 13:43:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636975#M42630</guid>
      <dc:creator>SSP_1</dc:creator>
      <dc:date>2001-12-31T13:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: omniback error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636976#M42631</link>
      <description>Probably the first thing I would do is to run nslookups for name and IP to make sure OBII is resolving properly.&lt;BR /&gt;&lt;BR /&gt;Just a quick thought to try,&lt;BR /&gt;Rita</description>
      <pubDate>Mon, 31 Dec 2001 14:07:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636976#M42631</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2001-12-31T14:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: omniback error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636977#M42632</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt; Most likely causes are 1) DNS / Network hostname resolutions problems - you could check using ping/nslookup or resolve hostnames first using /etc/hosts (files) via /etc/nsswitch.conf and ensure the cell manager and client are listed in here ? or 2) licensing .&lt;BR /&gt;&lt;BR /&gt;ps also check in /etc/opt/omni/cell_server, cell_info etc to make sure hostnames listed tie up with those returned from nslookup ie all entries are fully qualified domain names or short hostnames but not a mix of both it can cause problems.&lt;BR /&gt;&lt;BR /&gt;I'd post this to the openview forums , check the above and add the details to your post.&lt;BR /&gt;&lt;BR /&gt;also look in /vat/opt/omni/logs/* any clues ?&lt;BR /&gt;&lt;BR /&gt;Also of use : run omnicc &amp;gt;text.txt and details of whether this has ever worked, hpux versions or is NT involved, Version of OB II etc .... would be useful too !&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Dec 2001 14:07:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636977#M42632</guid>
      <dc:creator>Alex Glennie</dc:creator>
      <dc:date>2001-12-31T14:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: omniback error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636978#M42633</link>
      <description>Hi Shripad,&lt;BR /&gt;&lt;BR /&gt;Try these links,&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support3.external.hp.com/cki/bin/doc.pl/sid=a2f55cfd09d36c043a/screen=ckiDisplayDocument?docId=200000057865510" target="_blank"&gt;http://us-support3.external.hp.com/cki/bin/doc.pl/sid=a2f55cfd09d36c043a/screen=ckiDisplayDocument?docId=200000057865510&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support3.external.hp.com/cki/bin/doc.pl/sid=0a5c53b418c5c19dc1/screen=ckiDisplayDocument?docId=200000057865495" target="_blank"&gt;http://us-support3.external.hp.com/cki/bin/doc.pl/sid=0a5c53b418c5c19dc1/screen=ckiDisplayDocument?docId=200000057865495&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Dec 2001 21:17:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636978#M42633</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2001-12-31T21:17:45Z</dc:date>
    </item>
    <item>
      <title>Re: omniback error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636979#M42634</link>
      <description>Thanks Alex..&lt;BR /&gt;&lt;BR /&gt;I am able to see the hpux server in clients' list after adding it in file "/etc/opt/omni/cell/cell_info".&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 02 Jan 2002 08:48:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/omniback-error/m-p/2636979#M42634</guid>
      <dc:creator>SSP_1</dc:creator>
      <dc:date>2002-01-02T08:48:28Z</dc:date>
    </item>
  </channel>
</rss>

