Known problems and limitations in ESM

VeloCloud known problems and limitations

Issue Summary: The password for DCC and Kafka cannot be “changeme”.

Description: When the password is “changeme”, discovery for the VeloCloud orchestrator fails.

Workaround: Need to change the password for DCC and Kafka from "changeme".

Issue Summary: The name for the Orchestrator host instance in IP domain must be the IP address of the Orchestrator.

Description: Orchestrator host instance in IP domain must not be a DNS resolved name or anything other than the IP address. If it is, then the discovery for the VeloCloud orchestrator fails in the ESM server.

Workaround: If the name resolve to the DNS name then either use USESEEDNAME option to resolve the name or create the Orchestrator host using the below dmctl commands:

1. create Host::<ip address>
2. create SNMPAgent::SNMPAgent-<ip address>
3. create IP::IP-<ip address>
4. insert Host::<ip address>::HostsServices SNMPAgent::SNMPAgent-<ip address>
5. insert Host::<ip address>::HostsAccessPoints IP::IP-<ip address>
6. put SNMPAgent::SNMPAgent-<ip address>::AgentAddress <ip address>
7. get SNMPAgent::SNMPAgent-<ip address>::LayeredOver
8. insert SNMPAgent::SNMPAgent-<ip address>::LayeredOver IP::IP-<ip address>

Issue Summary: Only one Kafka partition is supported for the Kafka topic that is used for discovery..

Description: Only one Kafka partition is supported for the Kafka topic that is used for discovery.

Workaround: No workaround available.