1 of 1 people found this helpful
What do you have set as the BFF_ROOT (in the Property Dictionary - Custom Classes / AIX_Patching) ? and is that location mounted on all of your appservers?
Are you using the 'network deploy' functionality in here somewhere, otherwise I'm not clear what is trying to get back to the nfs mount point.
w/ out of box aix vpc it should be pulling the patches straight from the BFF_ROOT on the appserver (whichever appserver is running the job), to the target via the agent. the target should not be trying to nfs mount anything.
also, you don't want to have the repeater be a repeater for itself, it may work but it's adding an extra copy to the steps in the best case...
BFF_root is not set to any value.
My AIX guy is attempting to nfs mount the location of the bl package on the appserver. I believe his goal is to speed up the copying of the bl package to the target or to the repeater. Im not sure if this would buy him any time on the download.
his patch bundle would be over 1gb so he is trying any approach.
In this case the repeater is the only server he can patch at the moment.
URL Type -T
AGENT_MOUNT—A Deploy Job instructs the agent on
a target server to mount the device specified in the URL
and deploy patch payloads directly to the agent. To use
this option, the Network URL parameter must identify a
network location where patch payloads are stored.
Where are the packages stores, and is that exported via NFS ? and is that accessible from the target?
The patch location is a subfolder of an exported NFS mount. however, I dont know if it is a global mount.
I'd have to check with the admin to see if its exported as global.