The setup you are describing sounds ok - the important thing is to use the load balancer endpoints as service URLs for all cmp.properties but from your description I gather that's already what you are doing.
For simplicity you might consider a setup where you enable everything on all nodes. As long as you only have 5-10 nodes that should be ok.
- cmb.cqs.serviceEnabled=true
- cmb.cns.serviceEnabled=true
- cmb.cns.publisherEnabled=true
- cmb.cns.publisherMode=Producer,Consumer
Or, when you scale up you could enable CQS AND CNS on some nodes and producer AND consumer on some others like so:
- cmb.cqs.serviceEnabled=true
- cmb.cns.serviceEnabled=true
- cmb.cns.publisherEnabled=false
- cmb.cns.publisherMode=Producer,Consumer
- cmb.cqs.serviceEnabled=false
- cmb.cns.serviceEnabled=false
- cmb.cns.publisherEnabled=true
- cmb.cns.publisherMode=Producer,Consumer
This way you only have to manage two different configurations.
Don't worry about CQS showing as unavailable - I have a feeling this is a bug in the dashboard. Will have a look and fix if needed soon. You can and should test basic CQS / CNS functionality manually via Web UI though. It's quick and easy and it will give you a sense whether the service is operating properly.