<?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: EMS stating instance being set to DOWN as instance was not recognized by any monitor in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572369#M873579</link>
    <description>Hi Chris&lt;BR /&gt;&lt;BR /&gt;You put me in the right direction with bringing down the diagnostic.  I did do /sbin/init.d/diagnostic stop and /sbin/init.d/diagnostic start&lt;BR /&gt;&lt;BR /&gt;Then I went into sam under Resource Management and it said that the monitors were not available.  So what I did was I restarted the monitors under /usr/sbin/stm/uut/bin/tools/monitor.  I first brought down the monitors that were running and then I brought up disk_em and dm_memory.  I then went back into sam under resource management and all the disks were back to up and I did not get the error that the monitors were not available.  I then for the memory ran the set_fixed -n /system/status/memory/49 and that seemed to put my memory back to UP.  Thanks for all your help.</description>
    <pubDate>Thu, 30 Aug 2001 12:49:13 GMT</pubDate>
    <dc:creator>Troy Blangin</dc:creator>
    <dc:date>2001-08-30T12:49:13Z</dc:date>
    <item>
      <title>EMS stating instance being set to DOWN as instance was not recognized by any monitor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572365#M873575</link>
      <description>I installed the new patch for EMS (PHSS_23577) and after I installed the patch in the event.log it states for /system/status/memory/49 is != 0 and its current value is DOWN(1).  It also says thsi instance being set to DOWN as instance was not recognized by any monitor.  I know the memory is fine on my Server but I wondered if there was a way to bring this back to UP without rebooting my Server.  &lt;BR /&gt;&lt;BR /&gt;When I installed this patch on my Development server I had all my instances set to DOWN because the instance was not recognized by any monitor.  So I just rebooted the machine and all the instances were set back to UP.&lt;BR /&gt;&lt;BR /&gt;I hope I do not have to reboot the server to get the memory set back to UP.&lt;BR /&gt;&lt;BR /&gt;I also tried by using set_fixed and it will not set the memory back to UP.&lt;BR /&gt;&lt;BR /&gt;How do I set memory back to up without rebooting my Server.&lt;BR /&gt;&lt;BR /&gt;Hopefully someone can help me.  Thanks and have a nice day.</description>
      <pubDate>Wed, 29 Aug 2001 18:37:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572365#M873575</guid>
      <dc:creator>Troy Blangin</dc:creator>
      <dc:date>2001-08-29T18:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: EMS stating instance being set to DOWN as instance was not recognized by any monitor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572366#M873576</link>
      <description>do you have the EMS message to post up here?&lt;BR /&gt;It wouldn't by chance be entered into your /var/stm/data/tools/monitor/disabled_instances file?&lt;BR /&gt;&lt;BR /&gt;Let me know.&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Wed, 29 Aug 2001 18:45:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572366#M873576</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2001-08-29T18:45:37Z</dc:date>
    </item>
    <item>
      <title>Re: EMS stating instance being set to DOWN as instance was not recognized by any monitor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572367#M873577</link>
      <description>Hi Chris &lt;BR /&gt;&lt;BR /&gt;I do not have any thing in the file /var/stm/data/tools/monitor/disabled_instances.  But there is a file called /var/stm/data/tools/monitor/disabled_instances.  OK.  Thanks and have a nice day.</description>
      <pubDate>Wed, 29 Aug 2001 19:54:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572367#M873577</guid>
      <dc:creator>Troy Blangin</dc:creator>
      <dc:date>2001-08-29T19:54:36Z</dc:date>
    </item>
    <item>
      <title>Re: EMS stating instance being set to DOWN as instance was not recognized by any monitor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572368#M873578</link>
      <description>have you tried bouncing the diagnostics?&lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/diagnostic stop &lt;BR /&gt;/sbin/init.d/diagnostic start&lt;BR /&gt;&lt;BR /&gt;Just another thought.  Do you have the EMS message to post?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Chris</description>
      <pubDate>Thu, 30 Aug 2001 08:06:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572368#M873578</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2001-08-30T08:06:03Z</dc:date>
    </item>
    <item>
      <title>Re: EMS stating instance being set to DOWN as instance was not recognized by any monitor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572369#M873579</link>
      <description>Hi Chris&lt;BR /&gt;&lt;BR /&gt;You put me in the right direction with bringing down the diagnostic.  I did do /sbin/init.d/diagnostic stop and /sbin/init.d/diagnostic start&lt;BR /&gt;&lt;BR /&gt;Then I went into sam under Resource Management and it said that the monitors were not available.  So what I did was I restarted the monitors under /usr/sbin/stm/uut/bin/tools/monitor.  I first brought down the monitors that were running and then I brought up disk_em and dm_memory.  I then went back into sam under resource management and all the disks were back to up and I did not get the error that the monitors were not available.  I then for the memory ran the set_fixed -n /system/status/memory/49 and that seemed to put my memory back to UP.  Thanks for all your help.</description>
      <pubDate>Thu, 30 Aug 2001 12:49:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572369#M873579</guid>
      <dc:creator>Troy Blangin</dc:creator>
      <dc:date>2001-08-30T12:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: EMS stating instance being set to DOWN as instance was not recognized by any monitor</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572370#M873580</link>
      <description>Troy,&lt;BR /&gt;&lt;BR /&gt;Well, I'm glad to see that you were able to get your monitors restarted; and without a reboot (I know how the customer hates that!).  I'm also glad to see I was of some help.  Good luck to you in the future.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Chris</description>
      <pubDate>Thu, 30 Aug 2001 12:56:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-stating-instance-being-set-to-down-as-instance-was-not/m-p/2572370#M873580</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2001-08-30T12:56:26Z</dc:date>
    </item>
  </channel>
</rss>

