<?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: ICMP DISABLED in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157406#M222</link>
    <description>I understand.  If MS was a bit more secure we wouldn't be having this conversation :-) Thanks!</description>
    <pubDate>Mon, 12 Jan 2004 16:25:53 GMT</pubDate>
    <dc:creator>John Vitiello</dc:creator>
    <dc:date>2004-01-12T16:25:53Z</dc:date>
    <item>
      <title>ICMP DISABLED</title>
      <link>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157398#M214</link>
      <description>ICMP is turned off in some of our reginal areas.  I setup the hardware status polling task to only use SNMP and this works great.  The only problem is that the Status Icon for the server still shows RED under Ping and Green under SNMP and Management Agents.  Is there a way to show the server status as green if the requested management method (SNMP in this case) is working properly?</description>
      <pubDate>Tue, 06 Jan 2004 13:13:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157398#M214</guid>
      <dc:creator>John Vitiello</dc:creator>
      <dc:date>2004-01-06T13:13:25Z</dc:date>
    </item>
    <item>
      <title>Re: ICMP DISABLED</title>
      <link>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157399#M215</link>
      <description>Unfortunately HP SIM currently requires ICMP to be enabled to work.  However, this is something we are seriously investigating now - look for a near future version to add some capbilities in this area and for us to extend this over time.</description>
      <pubDate>Tue, 06 Jan 2004 17:05:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157399#M215</guid>
      <dc:creator>Scott Shaffer</dc:creator>
      <dc:date>2004-01-06T17:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: ICMP DISABLED</title>
      <link>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157400#M216</link>
      <description>When ICMP is disabled, I would assume some other managment protocols are still being allowed, such as UDP for SNMP and TCP for some ports. If HP were to modify HP SIM to have the option to not use ICMP for automatic discovery and reachability of a system there would be a loss of functionality. To avoid this, we could use alternate protocols to achieve similar functionality. For instance we could use TCP to try to connect to a port configured by you and based on errors returned detect if the system was offline or not. The question I would have is would this still be enabled on the network or are most all protocols being blocked by either the routers, switches and possibly a built-in firewall on the server? Or will say TCP ports 2301 for the web agent management still be allowed on the network?&lt;BR /&gt;&lt;BR /&gt;Assuming that at least one or two TCP ports are enabled, would they be the same ports for all systems, or will some systems have one set of ports and a different set have different ports enabled?&lt;BR /&gt;</description>
      <pubDate>Wed, 07 Jan 2004 12:18:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157400#M216</guid>
      <dc:creator>Scott Shaffer</dc:creator>
      <dc:date>2004-01-07T12:18:06Z</dc:date>
    </item>
    <item>
      <title>Re: ICMP DISABLED</title>
      <link>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157401#M217</link>
      <description>Sorry for the late reply, I was out of town.  Due to the wonderful MS vulnerabilities we turned off ping replies specifically :-)  SSL, HTTP, Telnet and FTP ports are open across our internal networks.</description>
      <pubDate>Mon, 12 Jan 2004 09:51:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157401#M217</guid>
      <dc:creator>John Vitiello</dc:creator>
      <dc:date>2004-01-12T09:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: ICMP DISABLED</title>
      <link>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157402#M218</link>
      <description>Scott -&lt;BR /&gt;&lt;BR /&gt;I know thiswill create a lot of overhead on the SIm server side, but why not just use snmp for device statuses and discoveries? It will take longer during the discovery and polling processes but that should eliminate the use of ICMP if nto wanted.</description>
      <pubDate>Mon, 12 Jan 2004 13:52:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157402#M218</guid>
      <dc:creator>Jadrice Toussaint</dc:creator>
      <dc:date>2004-01-12T13:52:20Z</dc:date>
    </item>
    <item>
      <title>Re: ICMP DISABLED</title>
      <link>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157403#M219</link>
      <description>That is what I have done as a work around.  The problem is that I can't get the device to turn green (for overall monitiring purposes)in SIM due to the failure of the original ping failure.</description>
      <pubDate>Mon, 12 Jan 2004 14:47:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157403#M219</guid>
      <dc:creator>John Vitiello</dc:creator>
      <dc:date>2004-01-12T14:47:30Z</dc:date>
    </item>
    <item>
      <title>Re: ICMP DISABLED</title>
      <link>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157404#M220</link>
      <description>We could use SNMP, but we were looking for something more uniquitous that could be used as a quick up/down poll.</description>
      <pubDate>Mon, 12 Jan 2004 15:53:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157404#M220</guid>
      <dc:creator>Scott Shaffer</dc:creator>
      <dc:date>2004-01-12T15:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: ICMP DISABLED</title>
      <link>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157405#M221</link>
      <description>Will the Disk Space threshold issues that I continue to have be addressed at the end of march?</description>
      <pubDate>Mon, 12 Jan 2004 16:01:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157405#M221</guid>
      <dc:creator>Jadrice Toussaint</dc:creator>
      <dc:date>2004-01-12T16:01:36Z</dc:date>
    </item>
    <item>
      <title>Re: ICMP DISABLED</title>
      <link>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157406#M222</link>
      <description>I understand.  If MS was a bit more secure we wouldn't be having this conversation :-) Thanks!</description>
      <pubDate>Mon, 12 Jan 2004 16:25:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/icmp-disabled/m-p/3157406#M222</guid>
      <dc:creator>John Vitiello</dc:creator>
      <dc:date>2004-01-12T16:25:53Z</dc:date>
    </item>
  </channel>
</rss>

