<?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: osiping problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/osiping-problem/m-p/3584197#M528740</link>
    <description>You may need to run the swconfig on the OTS product on the freshly ignited systems to make sure all the devices files get configured properly.</description>
    <pubDate>Tue, 19 Jul 2005 07:21:51 GMT</pubDate>
    <dc:creator>Jim Keeble</dc:creator>
    <dc:date>2005-07-19T07:21:51Z</dc:date>
    <item>
      <title>osiping problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/osiping-problem/m-p/3584196#M528739</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;We have few identical rp3410 with OSI configured and running on LAN2. The are built by a same Ignite-UX server and for OTS configuration, NSAP is the only thing that is different.&lt;BR /&gt;&lt;BR /&gt;On one of the platforms we can osiping other systems but when I tried to run the same osiping command on other platforms, I got the following error message.&lt;BR /&gt;"No local NET configured"&lt;BR /&gt;&lt;BR /&gt;then if I run otsnet command with the network ID, osiping works fine.&lt;BR /&gt;&lt;BR /&gt;any ideas.&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;Nan</description>
      <pubDate>Sun, 17 Jul 2005 21:23:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/osiping-problem/m-p/3584196#M528739</guid>
      <dc:creator>njia_1</dc:creator>
      <dc:date>2005-07-17T21:23:07Z</dc:date>
    </item>
    <item>
      <title>Re: osiping problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/osiping-problem/m-p/3584197#M528740</link>
      <description>You may need to run the swconfig on the OTS product on the freshly ignited systems to make sure all the devices files get configured properly.</description>
      <pubDate>Tue, 19 Jul 2005 07:21:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/osiping-problem/m-p/3584197#M528740</guid>
      <dc:creator>Jim Keeble</dc:creator>
      <dc:date>2005-07-19T07:21:51Z</dc:date>
    </item>
    <item>
      <title>Re: osiping problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/osiping-problem/m-p/3584198#M528741</link>
      <description>Does HP have a OSI traceroute utility ?</description>
      <pubDate>Tue, 19 Jul 2005 18:45:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/osiping-problem/m-p/3584198#M528741</guid>
      <dc:creator>njia_1</dc:creator>
      <dc:date>2005-07-19T18:45:14Z</dc:date>
    </item>
    <item>
      <title>Re: osiping problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/osiping-problem/m-p/7151638#M528742</link>
      <description>&lt;P&gt;It's 1o years too late, but i suspect you need to set the otsnet&lt;/P&gt;&lt;P&gt;Use command otsnet &amp;lt;NSAP with N selector set to 00&amp;gt;&lt;/P&gt;&lt;P&gt;mv36tmp#./otsnet 39756f00000000000000000001080009da8041&lt;U&gt;&lt;STRONG&gt;00&lt;/STRONG&gt;&lt;/U&gt; ****THIS IS OWN NSAP with Nsel =00&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are your N selectors different on the system that works without the otsnet command?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then use osiping&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Oct 2021 20:37:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/osiping-problem/m-p/7151638#M528742</guid>
      <dc:creator>steve_b</dc:creator>
      <dc:date>2021-10-12T20:37:46Z</dc:date>
    </item>
  </channel>
</rss>

