I've deployed a hardened repository and got multiple issues regarding network communication... In contrast to the NFS repositories where you'd only have a connection from the gateway server to the NFS server, your proxies need to talk to the repository directly and the repository also "talks" to the backup server...
I know it's documented well and as soon as you've got a suspicion regarding the network, you'd sniff or check the documentation, etc. But as long as you don't think about it, you're having troubles. Same regarding DNS issues: My hardened repository wannted to resolve FQDN's, but couldn't. I didn't know that it had to...
When deploying a hardened repository or a linux server, you first of all need the SSH connection for the deployment of the components. Why then not ship a little module with those components which would automatically check the connectivity to the server, the proxies, etc. Just like the test-option regarding the application aware processing/credentials: You see immediately if the connection is fine and if you'd have to do further steps like opening ports. Having such a test-area to check against all different kind of communication issues like DNS resolving or closed ports would save customers AND the support team a lot of time.
Hope you'll find the idea good as well.
Thanks!