<?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 Issue with SAN switch being monitored by ISEE setup in Insight Remote Support</title>
    <link>https://community.hpe.com/t5/insight-remote-support/issue-with-san-switch-being-monitored-by-isee-setup/m-p/3773918#M762</link>
    <description>Hi;&lt;BR /&gt;&lt;BR /&gt;One of the supported cu has reported that he has problem SAN switches SNMP traps were not accepted/received by OSEM running on another on a central management server. &lt;BR /&gt;&lt;BR /&gt;SAN switches (B-switches A7393A) are enabled for SNMP notifications and configured for SNMP traps as per osem documentation.&lt;BR /&gt;&lt;BR /&gt;Could anyone help me, how to check which event generator agent is configured on SAN switch. Interface between the event generator and event handler i.e., osem. How to configure the snmp traps on the switch and osem.&lt;BR /&gt;What does these mean?&lt;BR /&gt; agtcfgset command&lt;BR /&gt;&lt;BR /&gt; snmpmibcapset&lt;BR /&gt;&lt;BR /&gt;What is significance of community name and ip address?&lt;BR /&gt;&lt;BR /&gt;Following is the observation from osem logs:&lt;BR /&gt;04/05/2006 11:18:24 INFO  Crsm Version 7.2.2 on SMAD318FK34H054/10.1.1.200&lt;BR /&gt;04/05/2006 11:18:24 INFO  Starting Operational Mode: Customer Service Gateway&lt;BR /&gt;04/05/2006 11:18:24 INFO  Native SNMP trap listener thread starting&lt;BR /&gt;04/05/2006 11:20:12 INFO  a0101c8000BCD6B813F_1144228811906 Trap placed on queue: snmp_trap_1588.2.1.1.32_6_4 from sansw6\10.1.1.218&lt;BR /&gt;04/05/2006 11:20:12 INFO  Placing SNMP get order. Community: private IP: 10.1.1.218&lt;BR /&gt;04/05/2006 11:20:14 INFO  Loaded cpq_snmpMsg.properties&lt;BR /&gt;04/05/2006 11:20:15 INFO  a0101c8000BCD6B813F_1144228811906 Trap rejected: snmp_trap_1588.2.1.1.32_6_4_1588.2.1.1.1.8.5.1.3.x_3, cause: Lookup trap rejection&lt;BR /&gt;04/05/2006 11:20:25 INFO  a0101c8000BCD6B813F_1144228825234 Trap placed on queue: snmp_trap_1588.2.1.1.32_6_4 from sansw5\10.1.1.217&lt;BR /&gt;04/05/2006 11:20:25 INFO  Placing SNMP get order. Community: private IP: 10.1.1.217&lt;BR /&gt;04/05/2006 11:20:25 INFO  a0101c8000BCD6B813F_1144228825234 Trap rejected: snmp_trap_1588.2.1.1.32_6_4_1588.2.1.1.1.8.5.1.3.x_3, cause: Lookup trap rejection&lt;BR /&gt;04/05/2006 19:19:42 INFO  a0101c8000BCD6B813F_1144257582125 Trap placed on queue: snmp_trap_1588.2.1.1.32_6_4 from sansw5\10.1.1.217&lt;BR /&gt;04/05/2006 19:19:42 INFO  Placing SNMP get order. Community: private IP: 10.1.1.217&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Attached herewith the osem log file.&lt;BR /&gt;&lt;BR /&gt;Its a mission critical cu, needs help ASAP.&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;</description>
    <pubDate>Wed, 19 Apr 2006 08:20:08 GMT</pubDate>
    <dc:creator>tr10385</dc:creator>
    <dc:date>2006-04-19T08:20:08Z</dc:date>
    <item>
      <title>Issue with SAN switch being monitored by ISEE setup</title>
      <link>https://community.hpe.com/t5/insight-remote-support/issue-with-san-switch-being-monitored-by-isee-setup/m-p/3773918#M762</link>
      <description>Hi;&lt;BR /&gt;&lt;BR /&gt;One of the supported cu has reported that he has problem SAN switches SNMP traps were not accepted/received by OSEM running on another on a central management server. &lt;BR /&gt;&lt;BR /&gt;SAN switches (B-switches A7393A) are enabled for SNMP notifications and configured for SNMP traps as per osem documentation.&lt;BR /&gt;&lt;BR /&gt;Could anyone help me, how to check which event generator agent is configured on SAN switch. Interface between the event generator and event handler i.e., osem. How to configure the snmp traps on the switch and osem.&lt;BR /&gt;What does these mean?&lt;BR /&gt; agtcfgset command&lt;BR /&gt;&lt;BR /&gt; snmpmibcapset&lt;BR /&gt;&lt;BR /&gt;What is significance of community name and ip address?&lt;BR /&gt;&lt;BR /&gt;Following is the observation from osem logs:&lt;BR /&gt;04/05/2006 11:18:24 INFO  Crsm Version 7.2.2 on SMAD318FK34H054/10.1.1.200&lt;BR /&gt;04/05/2006 11:18:24 INFO  Starting Operational Mode: Customer Service Gateway&lt;BR /&gt;04/05/2006 11:18:24 INFO  Native SNMP trap listener thread starting&lt;BR /&gt;04/05/2006 11:20:12 INFO  a0101c8000BCD6B813F_1144228811906 Trap placed on queue: snmp_trap_1588.2.1.1.32_6_4 from sansw6\10.1.1.218&lt;BR /&gt;04/05/2006 11:20:12 INFO  Placing SNMP get order. Community: private IP: 10.1.1.218&lt;BR /&gt;04/05/2006 11:20:14 INFO  Loaded cpq_snmpMsg.properties&lt;BR /&gt;04/05/2006 11:20:15 INFO  a0101c8000BCD6B813F_1144228811906 Trap rejected: snmp_trap_1588.2.1.1.32_6_4_1588.2.1.1.1.8.5.1.3.x_3, cause: Lookup trap rejection&lt;BR /&gt;04/05/2006 11:20:25 INFO  a0101c8000BCD6B813F_1144228825234 Trap placed on queue: snmp_trap_1588.2.1.1.32_6_4 from sansw5\10.1.1.217&lt;BR /&gt;04/05/2006 11:20:25 INFO  Placing SNMP get order. Community: private IP: 10.1.1.217&lt;BR /&gt;04/05/2006 11:20:25 INFO  a0101c8000BCD6B813F_1144228825234 Trap rejected: snmp_trap_1588.2.1.1.32_6_4_1588.2.1.1.1.8.5.1.3.x_3, cause: Lookup trap rejection&lt;BR /&gt;04/05/2006 19:19:42 INFO  a0101c8000BCD6B813F_1144257582125 Trap placed on queue: snmp_trap_1588.2.1.1.32_6_4 from sansw5\10.1.1.217&lt;BR /&gt;04/05/2006 19:19:42 INFO  Placing SNMP get order. Community: private IP: 10.1.1.217&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Attached herewith the osem log file.&lt;BR /&gt;&lt;BR /&gt;Its a mission critical cu, needs help ASAP.&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Apr 2006 08:20:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/issue-with-san-switch-being-monitored-by-isee-setup/m-p/3773918#M762</guid>
      <dc:creator>tr10385</dc:creator>
      <dc:date>2006-04-19T08:20:08Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with SAN switch being monitored by ISEE setup</title>
      <link>https://community.hpe.com/t5/insight-remote-support/issue-with-san-switch-being-monitored-by-isee-setup/m-p/3773919#M763</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Chapter 5 of the OSEM Installation Guide should tell you how to set it up:&lt;BR /&gt;&lt;A href="http://h18023.www1.hp.com/support/svctools/OSEM/osem_setup.pdf" target="_blank"&gt;http://h18023.www1.hp.com/support/svctools/OSEM/osem_setup.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Apr 2006 10:04:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/issue-with-san-switch-being-monitored-by-isee-setup/m-p/3773919#M763</guid>
      <dc:creator>Liem Nguyen</dc:creator>
      <dc:date>2006-04-19T10:04:15Z</dc:date>
    </item>
  </channel>
</rss>

