<?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 SNMP Issue - server &amp;quot;accepted community name&amp;quot; values in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/snmp-issue-server-quot-accepted-community-name-quot-values/m-p/3459815#M8828</link>
    <description>When running "configure or repair agents" using the CMS, the target server being repaired accepted community names read-write value is being set to the following number:  9bfdf5fc-674f-408d-a905-fd4993884df1&lt;BR /&gt;&lt;BR /&gt;How can I set the CMS to push the read-write value that's correct for our network?  The read-only community name is being set properly and the snmp-trap agent community and desitnation values are being set properly.&lt;BR /&gt;&lt;BR /&gt;The global properties settings have both read and write community strings set correctly in the CMS.&lt;BR /&gt;&lt;BR /&gt;Any ideas why I receive that random number when reparing SNMP community values?&lt;BR /&gt;&lt;BR /&gt;Thanks for your time,&lt;BR /&gt;&lt;BR /&gt;Wade</description>
    <pubDate>Mon, 10 Jan 2005 14:45:18 GMT</pubDate>
    <dc:creator>Wade_13</dc:creator>
    <dc:date>2005-01-10T14:45:18Z</dc:date>
    <item>
      <title>SNMP Issue - server "accepted community name" values</title>
      <link>https://community.hpe.com/t5/server-management-systems/snmp-issue-server-quot-accepted-community-name-quot-values/m-p/3459815#M8828</link>
      <description>When running "configure or repair agents" using the CMS, the target server being repaired accepted community names read-write value is being set to the following number:  9bfdf5fc-674f-408d-a905-fd4993884df1&lt;BR /&gt;&lt;BR /&gt;How can I set the CMS to push the read-write value that's correct for our network?  The read-only community name is being set properly and the snmp-trap agent community and desitnation values are being set properly.&lt;BR /&gt;&lt;BR /&gt;The global properties settings have both read and write community strings set correctly in the CMS.&lt;BR /&gt;&lt;BR /&gt;Any ideas why I receive that random number when reparing SNMP community values?&lt;BR /&gt;&lt;BR /&gt;Thanks for your time,&lt;BR /&gt;&lt;BR /&gt;Wade</description>
      <pubDate>Mon, 10 Jan 2005 14:45:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/snmp-issue-server-quot-accepted-community-name-quot-values/m-p/3459815#M8828</guid>
      <dc:creator>Wade_13</dc:creator>
      <dc:date>2005-01-10T14:45:18Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Issue - server "accepted community name" values</title>
      <link>https://community.hpe.com/t5/server-management-systems/snmp-issue-server-quot-accepted-community-name-quot-values/m-p/3459816#M8829</link>
      <description>Also, its seems the read-write community name being push out via the CMS is always a different number whether it is being pushed out to the same target or different targets.&lt;BR /&gt;&lt;BR /&gt;Wade</description>
      <pubDate>Mon, 10 Jan 2005 15:13:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/snmp-issue-server-quot-accepted-community-name-quot-values/m-p/3459816#M8829</guid>
      <dc:creator>Wade_13</dc:creator>
      <dc:date>2005-01-10T15:13:29Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Issue - server "accepted community name" values</title>
      <link>https://community.hpe.com/t5/server-management-systems/snmp-issue-server-quot-accepted-community-name-quot-values/m-p/3459817#M8830</link>
      <description>Keep in mind that HP SIM doesn't require an SNMP write string; it only ever does read operations using SNMP.  However, the different agent modules use SNMP to flag things among themselves.  The write string is internal and never happens on the wire.&lt;BR /&gt;&lt;BR /&gt;With "C or R A" if a write string already exists, it will leave it alone.  In the absence of one, one gets set, but in order to avoid introducing a potential security hole, a long, random string is used.&lt;BR /&gt;&lt;BR /&gt;If you have a purpose for using SNMP writes outside the scope of HP SIM usage, once the "C or R A" has run, you have a trust relationship established that allows you to replicate the SNMP strings to all your servers.  &lt;BR /&gt;&lt;BR /&gt;So, if you have the correct write string set in your build process and thereafter need to use "C or R A" it will leave it alone.  If you don't have a right string set, you end up with a trust relationship that lets you set it from within HP SIM.</description>
      <pubDate>Mon, 10 Jan 2005 15:30:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/snmp-issue-server-quot-accepted-community-name-quot-values/m-p/3459817#M8830</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2005-01-10T15:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Issue - server "accepted community name" values</title>
      <link>https://community.hpe.com/t5/server-management-systems/snmp-issue-server-quot-accepted-community-name-quot-values/m-p/3459818#M8831</link>
      <description>Thanks David!</description>
      <pubDate>Mon, 10 Jan 2005 15:48:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/snmp-issue-server-quot-accepted-community-name-quot-values/m-p/3459818#M8831</guid>
      <dc:creator>Wade_13</dc:creator>
      <dc:date>2005-01-10T15:48:25Z</dc:date>
    </item>
  </channel>
</rss>

