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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
First, did you open a PMR of a defect on this issue? That's the first
thing that needs to be done, and I can't tell if that happened.
While "smit route" modifies the ODM inet0 object, "route" does not. So
deleting a route using "route" doesn't remove the equivalent attribute
from inet0. And apparently the code underlying "smit route" sees the
two routes you added as different, so it just adds the second one you
added rather than complain.
So rather than use "route" to delete the route, you could have used
"smit route" and selected "Remove a Static Route", or used
chdev -l inet0 -a delroute=net,-hopcount,0,,,,,,-static,172.16.22,192.168.132.249