<?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 Multi-homed SIM 5.0 server and SNMP traps in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/multi-homed-sim-5-0-server-and-snmp-traps/m-p/3701775#M17371</link>
    <description>I'm having trouble getting SIM to process SNMP traps on a multi-homed SIM server. I can see the traps come in on a packet trace, community string is correct, agent server is discovered in SIM, name resolution all looks good. It appears that SIM does process traps received on one interface but not all interfaces. I don't have enough info to be sure that's what is happening, but sending test traps seems to confirm it.</description>
    <pubDate>Tue, 03 Jan 2006 16:42:18 GMT</pubDate>
    <dc:creator>Dan Stebbins</dc:creator>
    <dc:date>2006-01-03T16:42:18Z</dc:date>
    <item>
      <title>Multi-homed SIM 5.0 server and SNMP traps</title>
      <link>https://community.hpe.com/t5/server-management-systems/multi-homed-sim-5-0-server-and-snmp-traps/m-p/3701775#M17371</link>
      <description>I'm having trouble getting SIM to process SNMP traps on a multi-homed SIM server. I can see the traps come in on a packet trace, community string is correct, agent server is discovered in SIM, name resolution all looks good. It appears that SIM does process traps received on one interface but not all interfaces. I don't have enough info to be sure that's what is happening, but sending test traps seems to confirm it.</description>
      <pubDate>Tue, 03 Jan 2006 16:42:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multi-homed-sim-5-0-server-and-snmp-traps/m-p/3701775#M17371</guid>
      <dc:creator>Dan Stebbins</dc:creator>
      <dc:date>2006-01-03T16:42:18Z</dc:date>
    </item>
  </channel>
</rss>

