Hi,

I had an issue with sending SNMP traps recently. Normally IBM iseries
listens for SNMP Manager on port 161 and sends SNMP traps to SNMP Manager
on Port 162.

Check CHGSNMPA settings.
Since you said the SNMP manager IP and Community Name are matching, ensure
Log Traps is set to *YES.
This way when an SNMP trap is sent from the agent it gets logged in the
journal QSNMP in QUSRSYS.
Do a DSPJRN on the QSNMP journal using todays date and verify the number of
entries and last entry time.

Secondly, start a trace to SNMP manager IP using SNMP manager IP using
TRCCNN.

End and Start SNMP service using ENDTCPSVR *SNMP and STRTCPSVR *SNMP, this
send a cold SNMP trap.
Check if the SNMP manager recieves the cold trap.

Generate a fake SNMP trap if possible from the iseries SNMP agent.

Do a DSPJRN on QSNMP in QUSRSYS and verify if there are new entries ( there
may be one approximatly when the cold trap was sent and another when you
initiated a fake SNMP trap.

Turn off the Trace.
This generates Spool Files.
One of spool files will show you on which port SNMP traps are being sent.

Regards,
Vik.


On Sat, Apr 4, 2015 at 6:55 AM, Bdietz400 <bdietz400@xxxxxxxxx> wrote:

I recall seeing a ptf to "fix" the ephemeral port issue

SI55487 7.1 OSP-SNMP SENDING RESPONSES VIA PORT 161, GETBULK
SUPPORT, AN
SI55537 7.2 OSP-SNMP SENDING RESPONSES VIA PORT 161, GETBULK
SUPPORT, AN
--
Bryan

On Apr 3, 2015, at 10:43 AM, Tim Bronski <tim.bronski@xxxxxxxxx> wrote:

Just for the record and for anyone interested... You will need to make
sure that any firewall between the ibm i and the snmp NMS allows all
inbound traffic to ports 161 and 162 of the NMS from the ibm i. Some
stateful firewalls have more limiting rules that require the request to
come FROM port 161 for responses. The ibm i doesn't do that - it picks an
ephemeral port above 5000.

On 4/1/2015 8:59 PM, Mike Cunningham wrote:
We have fixed out problem. SolarWinds supports SNMPv1, SNMPv2c and
SNMP3. It worked when we dropped it back to SNMPv1. Default is SNMPv2c
(with no option for v2b or plain v2)

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Tim Bronski
Sent: Wednesday, April 01, 2015 12:35 PM
To: Midrange Systems Technical Discussion
Subject: Re: SNMP on iSeries

I wasn't the person that set it up and I don't remember anything like
that but I can check into it later.

On 4/1/2015 6:22 PM, Mike Cunningham wrote:
I was reading one post that claimed the iSeries SNMP agent would
listen on port 161 but not respond using that port. It would respond using
port 5000. The manager that person was using was expecting the response on
the 161 port. Do you remember any issue like that with OpenNMS?

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Tim Bronski
Sent: Wednesday, April 01, 2015 12:14 PM
To: Midrange Systems Technical Discussion
Subject: Re: SNMP on iSeries

We use OpenNMS. In fact I was playing with some new MIBs today.

On 4/1/2015 5:22 PM, Mike Cunningham wrote:
Is anyone currently using a package like SolarWinds or SpiceWorks as
an SNMP Manager and have it collecting data from an iSeries SNMP
Client? We have SNMP active on the iSeries and can see QTMSNMPRCV
running and listening on port 161. Community names have been verified
between the Manager and Agent. Manager does not give any detail why
it can't contact the agent (iSeries), just reports that the test
failed. We are running V7.1. We are not using SNMP v3

Thanks
Mike Cunningham
--
Need secure FTP? Download your native sFTP solution here:
www.arpeggiosoftware.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at http://archive.midrange.com/midrange-l.
--
Need secure FTP? Download your native sFTP solution here:
www.arpeggiosoftware.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at http://archive.midrange.com/midrange-l.

--
Need secure FTP? Download your native sFTP solution here:
www.arpeggiosoftware.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.