IBM Power Ideas Portal
Hide about this portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add a new idea Subscribe
Status Submitted
Workspace IBM i
Categories Networking
Created by Guest
Created on Mar 26, 2025

RELATED IDEAS

Allow option to not log invalid OID requests as TCP4012 in job QTMSNMP

See this idea on ideas.ibm.com

It was discovered while a monitoring team had the IBM i LPARs set up in SolarWinds (SW) for SNMP monitoring that the QTMSNMP jobs were reaching maximum log size and ending. IBM support identified that among the OIDs SW was requesting were OIDs that the IBM i did not support. The SNMP server was sending back a "noSuchName" response but also logging a TCP4012 message in the QTMSNMP job. Frequency of the SW polling would fill the log and end the SNMP service within days. Options to address this would be to have SW stop polling for these OIDs (unknown if possible, still working with that team), change the logging level of the QTMSNMP job (not desired), change the JOBD or system value for full job log to *PRTWRAP (not desired), or cycle the SNMP server frequently to avoid the job log filling up (not desired but what is being done for now).

Note this is with authenticated SNMPv3 if relevant.

Even if the root cause of SW polling for invalid OIDs can be addressed this still brings to light that irresponsible or accidental polling of invalid OIDs on the IBM i SNMP server can cause it to end and impact monitoring. I would like it to be considered to add a new option into CHGSNMPA to not log the TCP4012 messages in the log for invalid OID request.

The idea that I've come up with...

CHGSNMPA Option: Log invalid OID requests
Values: *YES or *NO
Handling: With a *YES setting (default) the system would act as it does today. Send the "noSuchName" response to the requester and log a TCP4012 message in the joblog. A *NO setting would still have the server respond to the requester with "noSuchName", but would not log anything to the joblog.

Further possible enhancement, in handling with a *YES setting create a new message ID that instead of TCP4012 would be logged in the joblog, and in it include the offending OID request and requester IP. This would aid in tracking down what clients need to be addressed without having to capture and dissect a possibly encrypted packet trace.

Idea priority Low

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.