<?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 Data Collection found no data in HPE MSA Storage</title>
    <link>https://community.hpe.com/t5/hpe-msa-storage/data-collection-found-no-data/m-p/1005820#M4197</link>
    <description>I have a list of system both Linux and Windows that do have SNMP services running on them. Although, I have checked the SNMP Trap Service disabled or not started. However, I do receive information if the server is down or up or not responding. Is this sufficient that they just send info to the SIM server with a simple SNMP service set to the community Read Only database? Or should the SNMP trap also be started on each of the servers? Which is better?</description>
    <pubDate>Wed, 24 Sep 2008 16:41:41 GMT</pubDate>
    <dc:creator>NicholasN</dc:creator>
    <dc:date>2008-09-24T16:41:41Z</dc:date>
    <item>
      <title>Data Collection found no data</title>
      <link>https://community.hpe.com/t5/hpe-msa-storage/data-collection-found-no-data/m-p/1005820#M4197</link>
      <description>I have a list of system both Linux and Windows that do have SNMP services running on them. Although, I have checked the SNMP Trap Service disabled or not started. However, I do receive information if the server is down or up or not responding. Is this sufficient that they just send info to the SIM server with a simple SNMP service set to the community Read Only database? Or should the SNMP trap also be started on each of the servers? Which is better?</description>
      <pubDate>Wed, 24 Sep 2008 16:41:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-msa-storage/data-collection-found-no-data/m-p/1005820#M4197</guid>
      <dc:creator>NicholasN</dc:creator>
      <dc:date>2008-09-24T16:41:41Z</dc:date>
    </item>
  </channel>
</rss>

