You observe that the Performance Center (PC) loses contact with the Data Aggregator (DA), or you experience synchronization failures.
Below exception is seen in the PC DMServie.log:
jakarta.xml.ws.WebServiceException: org.apache.cxf.interceptor.Fault: Unmarshalling Error: Illegal character ((CTRL-CHAR, code <no>))
This issue is seen due to control and non-printable ASCII characters being processed by the VNA DNAC plugin.
You must update the regex in the DNAC plugin configuration to restrict hostnames to alphanumeric characters, digits, and a specific set of special characters (hyphens, underscores, dots, and spaces).
Follow these steps to implement the fix:
Stop the Wildfly service: systemctl stop wildfly
Delete the ActiveMQ data folder: rm -rf /opt/CA/VNA/wildfly/standalone/data/activemq
Clear the updates directory: rm -rf /opt/CA/VNA/data/updates/*
Backup the configuration file: Create a backup of /opt/CA/VNA/plugins/DNAC Plugin/config/inventory/client.perspective in a secure location outside of the VNA directory tree.
Modify the configuration file: Edit /opt/CA/VNA/plugins/DNAC Plugin/config/inventory/client.perspective and replace the getDisplayName method with the code below and ensure the indentation is consistent with the existing data.
def getDisplayName( hostName )
{
if( hostName == null || hostName == '' )
{
return 'Unnamed Client'
}
// Allow only alphanumeric, dot, dash, underscore, and space
def displayName = hostName.replaceAll("[^a-zA-Z0-9._\\-\\x20]", "").trim()
if( displayName.isEmpty() )
{
return 'Unnamed Client'
}
return displayName
}
Start the Wildfly service: systemctl start wildfly
Monitor the logs: Check /opt/CA/VNA/wildfly/standalone/log/gateway.log for any errors during startup or synchronization.
Verify connectivity: Wait for several minutes and verify if the Performance Center successfully establishes contact with the Data Aggregator.
http://<da>:<port>/rest/sdngatewayshttp://<da>:<port>//action/sdngateway/<sdngatewayid>/inventory/resyncIf the connectivity issue remains unresolved after implementing these steps, please open a case with Broadcom Support for further investigation.