I have installed 8.1 vRealize Orchestrator cluster with 3 nodes . When you read the documentation and you will ask yourself a question do i really need 3 nodes instead of 2, then the answer is yes, you need 3 nodes to install it, that’s what i was told by VMware support, although the documentation uses word ‘recommended 3 nodes’. Anyway… so you replaced your certificates, cluster is installed, and you try to do snmp trap towards it, and it fails. The workflow that listens for trap on all devices is just waiting…
So again you have to do the trick with the snmp port (by default its the 4000 udp to your orchestrator unless you changed it).
As described here:
you when you have 3 node cluster, you have to do this on 3 vro servers.
After this is completed, you have to go to your load balancer and add new rules for port 4000 udp as well.
without adding new service on port 4000 udp, the cluster would still not receive the trap. After this, your cluster will receive the snmp traps without a problem.
for this 4000 udp service, you can also put for monitor 8008 /health i suppose, i mean if vro is down then the snmp should be also not available.
1 other thing to mention, your certificate for vro8 cluster should be composed with CN of LB fqdn, not the leading node. I think i read it in some book that this owuld have to be CN of first node, but i was told by the VMware support today, that in CN i should put the cluster LB FQDN.
[ req ]
default_bits = 2048
distinguished_name = req_distinguished_name
req_extensions = req_ext
prompt = no
[ req_distinguished_name ]
countryName = NL
stateOrProvinceName = NoordHolland
localityName = Amsterdam
organizationName = HomeLabs
commonName = vrocluster81.greg.labs
[ req_ext ]
subjectAltName = @alt_names
DNS.1 = vro811.greg.labs
IP.1 = 192.168.10.31
DNS.2 = vro812.greg.labs
IP.2 = 192.168.10.32
DNS.3 = vro813.greg.labs
IP.3 = 192.168.10.33
DNS.4 = vrocluster81.greg.labs
IP.4 = 192.168.1.211