Configure HTTP proxy in SUMA

UNIX AIX
1

Hi,

        I am trying to configure an HTTP_PROXY so that suma can reach out  beyond our intranet and pull updates from the IBM website. Currently,  our suma config is the default as it's not been used before. When I  attempt to issue the following command sudo suma -c -a HTTP_PROXY=http://our-proxy.location.company.com:8080/ I get the following error 0500-019 The -a flag entry HTTP_PROXY=http://our-proxy.location.company.com:8080/ is not valid.     
              
        I know this proxy is working, as it is being use elsewhere with no  issues. I'd like to get this tool working as it seems to be the easiest  method of bringing patches into our environment, so any advice will  certain help! Thank you.
2

Probably the trailing / after :8080 should not be there..

3

I tried removing it already to no avail. What I did find is that SUMA no longer allows you to define the HTTP proxy within SUMA itself. I need to use srv_conn to edit it. I'll go ahead and test that now.

Thank you for your reply.

EDIT: I configured the HTTP proxy, now the preview command is yielding

****************************************
Performing preview download.
****************************************
0500-059 Entitlement is required to download.
The system's serial number is not entitled.
Please go to the Fix Central website to download fixes.

But, I can go to Fix Central myself and input this machines serial and machine type and download fixes Manually. Ugh.

4

Starting with AIX 7.1 the http proxy is no longer an environment variable. Instead, you configure the proxy via the electronic service agent.

As you noted, the fastpath to that is " smitty srv_conn ". I did not realize that was the fast path :stuck_out_tongue: at me.

5

Yeah, I had just noticed that in the man page for suma. Unfortunately configuring the http proxy successfully still hasn't yielded the results I need as IBM is complaining that the serial does not have any software entitlement, which is funny, because I just checked on Fix Central and it does. Fun stuff!

6

I have been waiting for the day - rather fearing the day - when SUMA would also be checking the serial number.

In the back of my mind I am thinking the check is not SUMA, but the electronic service agent saying you are not "support ready".

In any case - also get your IBM service contact involved, perhaps opening a PMR.

7

Thanks for the reply. I did get them involved, and their "solution" is to just manually download all of the fixes myself and perform manual patching. Well, in such a big environment I don't think that's really an acceptable response. Guess I need to escalate with them past first line support.

EDIT: Does ESA need to be installed for suma to work?

8

When helping customers setup PowerSC the proxy has worked fine with esa being configured on the system but not used to submit anything. It is just a "proxy" connection. When setting it up I/we use the test connection through the proxy.

Remember - you are using the proxy because your system does not have direct access. ESA has the proxy configuration because the system does not have direct access. SUMA just borrows this connection path.

re: your previous support/PMR: Definitely escalate. That is not a solution.

However, the first step when working with support will be to verify you can submit something via ESA (if I recall that also requires an active support contract). Since they are talking with you - you have passed that hurdle already.

In short, if you can submit a test ticket using ESA then you can add that "as a fact", and that you expect IBM to make it work. Whether you are or not - say you are evaluating PowerSC component - TNCPM (Trusted Network Connect/Patch Management) as the PM compoment will not work unless the system can connect to SUMA for downloads. FixCentral downloads do not suffice!