Administration > Integration > VCF Adapter > expand VCF Instance > Edit vCenter Server Endpoint > Log Operations and enabling “Activate log collection” under Collect Logs (using the “Collect logs using the collector/group” option) completes successfully.Infrastructure Operations > Configurations > Log Collection, an error appears stating “Failed to propagate configuration to CP.”

vcf-log-forwarder/log-forwarder.log in Cloud proxy
ERROR c.v.l.l.c.LogCollectionConfigScheduler:### - Error while fetching and applying log collection configurations.
com.vmware.log.forwarder.httpclient.APIException: Got status 503 while retrieving session.
at com.vmware.log.forwarder.logservercredentials.LogServerSession.refreshSession(LogServerSession.java:##)
at com.vmware.log.forwarder.logservercredentials.LogServerSession.getSession(LogServerSession.java:##)
/var/log/HAproxy-traffic.log in cloud proxy localhost haproxy[#####]: Server PrxyRC_VRLI_BE/VRLI_2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 156ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.localhost haproxy[#####]: backend PrxyRC_VRLI_BE has no server available!VCF Operations 9.0.1
VCF Operations for logs 9.0.1
This issue is caused by firewall restrictions, as the necessary ports (9543, 514, 6514, 1514) are not open between the cloud proxy and all VCF operations for log nodes, as detailed in the port requirements documentation.