Known Issues

This section describes the known issues and workarounds, if any:
nfa950
This section describes the known issues and workarounds, if any:
IPV6 Host Data Does Not Support CA Digital Operational Intelligence 1.2.2
This release does not support IPV6 host data with CA Digital Operational Intelligence 1.2.2
Pump Service Fails to Start after Upgrade
Problem:
The pump service fails to start after upgrade.
Solution:
Verify the connection errors in the pump log. Ensure all the services are up and running and restart the pump service.
If you notice any exception that is related to “Invalid file format”, delete the content in
$INSTALL_DIR/REPORTER/datafiles/input/Staging
and start the pump service.
Network Flow Analysis
 / CA Unified Infrastructure Management Integration
SNMP Profile Synchronization
SNMP profile synchronization is one way; that is, any changes that are made in 
Network Flow Analysis
 will not sync to CA Unified Infrastructure Management.
Installation and Upgrade
MySQL Upgrade Failure
Problem:
While upgrading 
Network Flow Analysis
, the installer generates the following error:
MySQL Upgrade Failure
MySQL Upgrade has failed. Please see 
install_path
\MySql_Upgrade_Log.log for more information.
This error indicates that the 
mysql_upgrade
 utility failed for unknown reasons while upgrading MySQL versions, and the schema migrator could not be run.
Solution:
  1. Contact CA Support for assistance
  2. Resolve the issue preventing
     mysql_upgrade
     from completing successfully. See the 
    MySQL Upgrade Failure
     dialog for the log file location.
  3. Run 
    mysql_upgrade
     for each instance that failed.
  4. Restart both the CA MySQL and NetQoS NQMySql services.
  5. Run the schema migrator:
    • Windows
      cmd /C cscript
      install_path
      \migrator\runMigrator.vbs
    • Linux
      install_path
      \migrator\runMigrator.sh
  6. Restart the system.
MySQL Error Messages in Windows Event Log
Problem:
You see MySQL errors in the Windows Event Log during an upgrade from CA NFA 9.3.3 to CA NFA 9.3.8.
Solution:
The 
Network Flow Analysis
 upgrade from 9.3.3 to 9.3.8 includes an upgrade from MySQL 5.6 to MySQL 5.7. The errors occur during the time between when the MySQL 5.7 files are installed on disk and the actual MySQL 5.7 upgrade. These errors can be safely ignored.
NFA Login Over SSL Fails After Upgrading to NFA 9.3.8
Problem:
Internet Explorer Error:
Internet Explorer cannot display the webpage
Mozilla Firefox Error:
Unable to connect
Firefox can't establish a connection to the server at <Console_address>
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
Solution:
Reconfigure the SSL. For more information, see Enable TLS for CA Network Flow Analysis.
Issue with Adobe Flash Player on Internet Explorer 11
Network Flow Analysis
 pages that use Adobe Flash Player (on the 
Administration
 page, 
Interfaces, Physical & Virtual
Interfaces, Enable Interfaces
) will not display correctly in the following context:
  • Windows 8 or Windows Server 2012
  • Internet Explorer 11
  • Adobe Flash Player Version 18.0.0.160 and later
Registering 
Network Flow Analysis
 with Performance Center
If you register 
Network Flow Analysis
 as a data source with CA PC or NPC before the CA NFA installation is complete, there could be synchronization issues.
Requirements for Naming Custom Installation Directories
If you install 
Network Flow Analysis
 software to a custom directory, make sure that no spaces or underscores are included in the installation path or directory name. In addition, use non-accented, alphanumeric characters from the ASCII character set. Non-English characters are not supported.
If you install 
Network Flow Analysis
 in an environment that is localized for Chinese or Japanese, make sure that you use only ASCII characters for directories in the installation path.
The installation will complete without any easily detected warnings in spite of the invalid path or directory names, but a series of problems occur when you start to use the software.
Installation and Upgrade Prerequisite Checks
Several prerequisite checks are performed during an installation or upgrade to help you avoid failure. The prerequisite checks are designed to detect some obvious problems, but the checks are not comprehensive. You are responsible for preparing and configuring your servers appropriately.
Uninstallation Support
The Uninstall option has the following limitations:
  • The Uninstall option cannot remove the product if it has been upgraded at any point from CA NetQoS ReporterAnalyzer 9.0.1 (9.0 upgrade 1). The Uninstall program completes successfully, but leaves the system in a state that does not support successful reinstallation of the software. In this case, the Custom Storage Engine (NetQoS NQMySql) service cannot be started.
    To recover from this situation, re-image the system and re-install the software.
    We support using the Uninstall for new installations and for software that has been upgraded from 
    Network Flow Analysis
     versions 9.1.00 through 9.3.6.
  • The Uninstall option can remove the MySQL software only if 
    Network Flow Analysis
     was installed before any other related software.
  • Other related software that is co-installed with 
    Network Flow Analysis
     is disabled by uninstalling 
    Network Flow Analysis
    .
  • Some directories and files are not removed during uninstallation (such as 
    \CA\NFA
    ). You have the option to remove these directories and files manually.
  • On a singlebox installation, running the Console uninstall removes files necessary for the Harvester to run (such as the JRE). To switch from a singlebox installation to a Harvester-only installation, you need to uninstall everything and then re-install the Harvester.
  • After an uninstall and attempted reinstall, the 
    Network Flow Analysis
     9.3.8 Console is unreachable. To successfully reinstall 
    Network Flow Analysis
     after an uninstallation on the same system:
    1. In the 
      Control Panel
      Folder Options
      View
       tab, 
      Advanced Settings
      , select 
      Show hidden files, folders, and drives
      .
    2. Navigate to
      C:\Program Files\Zero G Registry\
    3. Rename
      .com.zerog.registry
      to
      .com.zerog.registry_backup
    4. Remove the NetQoS MySql service on each system with a CA component. From a command line:
      sc delete "NetQoS MySql"
    5. If running the singlebox (stand-alone) configuration, run the Harvester installer.
    6. Run the Console installer.
    7. Delete the newly created
      .com.zerog.registry
    8. Rename
      .com.zerog.registry_backup
      to
      .com.zerog.registry
Previous Button in Harvester and Console Installation Program
The installation program for the Harvester and for the NFA console has a nonfunctional 
Previous
 button on the 
Choose Install Folder
 page. If you click the 
Previous
 button on this page, the program does not return you to the previous page. In addition, the 
Previous
Next
, and 
Cancel
 buttons become inactive.
If you encounter this problem, take one of the following actions:
  • Modify the installation directory to reactivate the 
    Next
     button.
  • Close the installation program and restart installation.
FATAL Error During 
Network Flow Analysis
 9.3.8 Migration
The below ERROR messages will be seen in 
CA\NFA\MySql_Backups\Backup.log
 during a migration to 9.3.8, however, these errors will NOT affect the functionality of the product. These are mysql errors that are part of STDERR because the 
Network Flow Analysis
 product does not use the MySQL innodb storage engine. These ERRORS can be safely ignored.
ERROR 1146 (42S02) at line 62: Table 'mysql.innodb_table_stats' doesn't exist ERROR 1243 (HY000) at line 63: Unknown prepared statement handler (stmt) given to EXECUTE ERROR 1243 (HY000) at line 64: Unknown prepared statement handler (stmt) given to DEALLOCATE PREPARE ERROR 1146 (42S02) at line 66: Table 'mysql.innodb_index_stats' doesn't exist ERROR 1243 (HY000) at line 67: Unknown prepared statement handler (stmt) given to EXECUTE ERROR 1243 (HY000) at line 68: Unknown prepared statement handler (stmt) given to DEALLOCATE PREPARE ERROR 1146 (42S02) at line 81: Table 'mysql.slave_relay_log_info' doesn't exist ERROR 1243 (HY000) at line 82: Unknown prepared statement handler (stmt) given to EXECUTE ERROR 1243 (HY000) at line 83: Unknown prepared statement handler (stmt) given to DEALLOCATE PREPARE ERROR 1146 (42S02) at line 110: Table 'mysql.slave_master_info' doesn't exist ERROR 1243 (HY000) at line 111: Unknown prepared statement handler (stmt) given to EXECUTE ERROR 1243 (HY000) at line 112: Unknown prepared statement handler (stmt) given to DEALLOCATE PREPARE ERROR 1146 (42S02) at line 128: Table 'mysql.slave_worker_info' doesn't exist ERROR 1243 (HY000) at line 129: Unknown prepared statement handler (stmt) given to EXECUTE ERROR 1243 (HY000) at line 130: Unknown prepared statement handler (stmt) given to DEALLOCATE PREPARE ERROR 1146 (42S02) at line 1894: Table 'mysql.slave_master_info' doesn't exist ERROR 1146 (42S02) at line 1895: Table 'mysql.slave_master_info' doesn't exist ERROR 1146 (42S02) at line 1896: Table 'mysql.slave_master_info' doesn't exist ERROR 1146 (42S02) at line 1897: Table 'mysql.slave_worker_info' doesn't exist ERROR 1146 (42S02) at line 1898: Table 'mysql.slave_relay_log_info' doesn't exist ERROR 1146 (42S02) at line 1902: Table 'mysql.innodb_table_stats' doesn't exist ERROR 1146 (42S02) at line 1906: Table 'mysql.innodb_index_stats' doesn't exist FATAL ERROR: Upgrade failed
NFA Console
Port Priorities Fails to Map the Port Correctly
The out-of-the-box Port Priorities, and any new user-defined Port Priorities, will not work unless other application mappings are already in place.
Workaround:
  • Restart the Harvester to get a new cache.
  • Add or update an Application Mapping Rule.
  • Touch the 
    AppMapUpdateTime
     entry in the parameter descriptions table on the Harvester to create a new timestamp.
Scheduled Reports on Linux Harvesters
On Linux Harvesters that are involved in scheduled reports, you might notice memory growth over time with repeated execution of reports. If this memory growth becomes problematic, you can schedule a custom storage engine restart using 
crontab
. The following command needs to be run as root in 
crontab
:
/etc/init.d/nfa_mysqlCSE restart
Note that restarting the custom storage engine will NOT impact data integrity. The only impact would be on any reports that are scheduled to run at the time of the restart.
False Alarms on the System Status Page
False alarms appear on the 
System Status
 page during an initial period after you add a Harvester in the NFA console. It is expected that Harvesters do not pass some system checks until they are fully functional. For example, you might see false alarm status messages that mention the following Harvester problems:
  • Zero value for the Last Load Timestamp and Watchdog polling time
  • Unknown usage for memory and disk
  • Unknown or high usage for CPU
  • Unknown or stopped state for services
False alarms typically clear up within an hour of component startup. In some cases, however, the false alarms continue.
If you suspect that the 
System Status
 page continues to list false alarms, restart the Watchdog service on the standalone or NFA console server. The current false alarms are cleared from the 
System Status
 page and no new false alarms are posted.
Show Device Name
You are allowed to set an Application Setting to remove Device Names from view. If you set 
Show Device Name
 to 
false
, it removes the Device Name for views in the NFA Console 
Interfaces
 page. However, it does NOT remove them for 
Enterprise Overview
 and 
Custom Reports
.
Harvester
Deleting a Harvester from the Console
If you delete a Harvester from the 
Network Flow Analysis
 9.3.8 Console, you cannot add the same Harvester instance again successfully unless the Harvester software has been completely uninstalled and re-installed. Once you delete a Harvester, you cannot recover any of the data that the Harvester collected.
Problems from Exporting Flow to Multiple Harvesters
Make sure that you configure flow export to be directed to a single Harvester.
You can clone the flow from Harvesters and forward it to other destinations by using the Flow Cloner feature.
Performance Center
Error Opening CA NetQoS Performance Center
An error message might open when you attempt to log in to the Single Sign-On program or click the 
NPC
 link in the NFA console under the following conditions:
  • Network Flow Analysis
     and CA NetQoS Performance Center 6.1 are installed on the same system (this is not a supported configuration)
  • CA NetQoS Performance Center 6.1 was installed after 
    Network Flow Analysis
In this case a Page Not Found (404) error opens. The program cannot locate the CA NetQoS Performance Center Console because a mixture of forward and backward slashes are used in some directory paths.
Note: This issue applies to deployments that include CA NetQoS Performance Center. If your deployment includes CA Performance Center, this issue does not apply to you.
Workaround:
Complete the following steps to define in the virtual path directories with backward slashes.
  1. Log in to the NFA console server as a user with administrator privileges.
  2. Open the Internet Information Services (IIS) Manager: Select 
    Start
    Administrative Tools
    Internet Information Services (IIS) Manager
    .
  3. Expand the tree in the left pane to display the virtual directories:
    1. Click the plus sign next to the server name.
    2. Expand the 
      Sites
       node. The virtual directories appear at the end of the list.
  4. Select one of the virtual directories (for example, ProxyServices).
  5. Click the
     Basic Settings
     link in the right pane. The 
    Edit Application
     dialog opens.
  6. Replace any forward slashes in the Physical path value with backward slashes.
  7. Click 
    OK
     to save any changes you made.
  8. Repeat the steps to make the correction for each remaining virtual directory.
'Access Denied' Error for LDAP Users
Users with LDAP-generated accounts might get an "Access Denied" error message when they attempt to log in or to drill in to 
Network Flow Analysis
 from Performance Center. The problem can be caused by one of the following conditions:
  • The SSO LDAP configuration is set up with inadequate product permissions to allow access.
  • An administrator configures the Single Sign-On program to enable the automatic creation of user accounts at LDAP sign-in. If the configuration is modeled on a user account that lacks the proper product permissions, the LDAP users who are created cannot drill in to the NFA console from Performance Center.
  • The LDAP user attempts to drill in before the account information is synchronized between the products. LDAP users acquire product permissions when synchronization is complete.
  • The LDAP user attempts to log in to the NFA console before logging in to the Performance Center Console. To create an LDAP-generated user accounts properly, users first must log in to the Performance Center Console. If you attempt to log in to the NFA console first and are denied access, log in to the Performance Center Console, then wait for your user account data to be synchronized with the NFA console.
  • The user account was created from a properly configured LDAP model, but the user account was changed later in a way that blocks access.
  • An outdated SSO LDAP configuration is in use, which has not been updated since the deployment was upgraded from CA NetQoS ReporterAnalyzer release 9.0.1. Reconfigure the SSO LDAP settings as described in the  article in the CA Performance Management documentation.
Complete the following tasks to ensure that LDAP users can drill in:
  1. Configure the LDAP settings for the Single Sign-On (SSO) program. For information about this task, see the  article in the CA Performance Management documentation. If you need further assistance, contact CA Support.
  2. Verify that the LDAP settings can be used to authenticate users successfully, as described in the "Validate LDAP Settings" topic in the 
    Single Sign-on
     article.
  3. Create a test case by having a user log in with an LDAP account.
  4. Check the user product permissions in the Manage Users page (CA PC) or User List page (NPC).
  5. If necessary, revise the model for LDAP configuration to correct any permission problems, then repeat steps 2 through 4.
  6. Wait 10 minutes for the next synchronization or perform a Resync on the 
    Manage Data Sources
     page (CA PC) or the 
    Data Source List
     page (NPC).
  7. Verify that the user can drill in to the NFA console from a view in the Performance Center Console. For example:
    1. Click an interface in the 
      Top Flows By Interface - Out
       view on the 
      Infrastructure Management
       page.This action opens the CA Performance Center 
      Interface Pages
      .
    2. Click the IP Performance tab. and click a link in the 
      Host Name
       column of the 
      Top Hosts (Pie) - Out
       view.
      The test user drills in to the NFA console without an Access Denied error message: The NFA console opens to the Interfaces page for the selected host.
Interface Names and Descriptions
Interface names and descriptions might not match between the NFA console and the CA Performance Center Console.
Changes to the interface names and descriptions are limited to the product that you use to make the changes. If you change interface descriptions in one product console, the changes are not displayed in the other console, for example. To show the same interface names and descriptions in both locations, make revisions in one product to match the other product.
NFA Console
  • The interface name and description is formatted as defined by the interface template, which uses the following values by default:
    • Interface Name: ifName or ifDescr value, whichever is found first
    • Interface Description: portName or ifAlias value, whichever is found first
  • To customize interface names and descriptions individually, use the 
    Active Interfaces
     page.
    Any changes you make are shown in a number of locations, including the 
    Active Interfaces
     page, 
    Enterprise Overview
     reports, drilldown Interface page reports, and the Interface Index. You use the 
    Interface Index
     to select interfaces as filters in Custom reports and Analysis reports and to navigate to an interface in the Interface pages.
CA Performance Center Console
  • The CA Performance Center Interface Details, Inventory pages, and trend views display interface names and descriptions that use the following default values:
    • Interface Name: ifName, ifDescr, or "Interface {ifIndex}" value, whichever is found first
    • Interface Description: ifDescr value, unless you apply an Interface Description Override to the parent domain
  • To customize interface descriptions, apply an Interface Description Override when you create a domain. To change the Interface Description Override settings for an existing domain, complete the following steps:
    1. Prepare a 
      .csv
       file with the interface description overrides that you want to use. Include the following columns and populate a row for each interface whose description you want to override: Device IP, Name, Description, and Interface Description Override.
    2. Log in to the CA Performance Center Console as a user with administrator privileges.
    3. Select 
      Admin
      IP Domains
      . The 
      Manage IP Domains
       page opens.
    4. Select the domain that you want to edit.
    5. Click 
      Edit
      . The 
      IP Domains Administration
       dialog opens.
    6. Click 
      Browse
       next to the 
      Interface Description Override
       field.
    7. Locate and select the .csv file that contains the appropriate overrides.
    8. Click 
      Save
       in the 
      IP Domains Administration
       dialog. The dialog closes.
    9. Resynchronize the 
      Network Flow Analysis
       data source:
      1. Select 
        Admin
        Data Sources
         from the console menu bar. The 
        Manage Data Sources
         page opens.
      2. Select the 
        Network Flow Analysis
         data source.
      3. Click 
        Resync
        . The data source is resynchronized.
        You can wait 5 minutes for the next synchronization to complete automatically instead of resynchronizing manually.
    10. Verify that the overrides have been applied in the 
      Interface Details
       page, 
      Inventory
       pages, and trend views.
The interface descriptions apply to devices that have already been discovered and to devices that will be discovered in the future.
Data Collection
Trap Definitions
Creating a trap definition with an apostrophe (') in the 
Description
 field can cause a 
500 Internal Server Error
. The workaround is to remove any apostrophes from the 
Description
.
Traps Using Utilization Thresholds
If you need to configure traps for interfaces using utilization thresholds, you must first ensure that the interfaces the traps are configured for are either SNMP-enabled and pollable by NFA, or have had their ifSpeed set manually through the NFA console. SNMP enabling interfaces is the preferred best practice.
Reports
Reports in Firefox Are Blurry
When displaying a report in Firefox that contains large amounts of data, the report might appear blurry and difficult to read.
Workarounds:
  • Download the report and view it in your local copy of Adobe Acrobat Reader.
  • View the report in Internet Explorer.
Error When Running Flow Forensics Report
When running Flow Forensics reports on a large amount of data with a 15-minute time frame they work fine. Longer time frames can cause the reports to error out with:
Error executing Flow Forensics report on host x.x.x.x
Follow these steps:
  1. Stop the CA NFA Hunter Tracker Service.
  2. Run the Flow Forensics reports (with > 15 minute time frames).
  3. Restart the CA NFA Hunter Tracker Service.
Copying Reports Might Not Work
A user with the Manage Reports right might not be able to copy all reports that they have visibility to. The workaround is to create a new report instead of copying an existing report.
Reports Might Not Be Visible After Upgrade
After an upgrade, a user with the Manage Reports right might not be able to see reports, report folders, or interfaces that were previously visible to them. The Administrator must grant these users access to the reports, report folders, or interfaces that they require access to.
Error Creating Custom or Analysis Reports
An error message might open when you attempt to create a Custom Report or Analysis report. This error message includes the text string "System UnauthorizedAccessException." The error occurs because insufficient permissions are assigned to the Internet Guest User Account (IUSR).
On a Windows Server 2012 R2 server, the report is created in spite of the error message.
To correct the problem, complete the following steps.
  1. Log in to the NFA console as a user who has administrator privileges.
  2. Open the 
    Component Services
     window:
    1. Select 
      Start
      Run
      .
      In the 
      Run
       window, enter 
      dcomcnfg
      .
    2. Click 
      OK
      . The 
      Component Services
       window opens.
  3. Display the nqreporter properties:
    1. Expand the following nodes in the left pane:
      • Component Services
      • Computers
      • My Computer
      • DCOM Config
    2. Locate the nqreporter service under DCOM Config.
    3. Right-click nqreporter and select 
      Properties
       from the context menu. The nqreporter 
      Properties
       window opens.
  4. Display the nqreporter group and user launch permissions:
    1. Click 
      Security
      . The 
      Security
       tab opens.
    2. Select the 
      Customize
       radio button in the 
      Launch and Activation Permissions
       section.
    3. Click 
      Edit
      . The 
      Launch and Activation Permissions
       dialog opens.
  5. Verify that the IUSR exists:
    1. Click 
      Add
       if the following account is not shown in the "Group or user names" list.
      • Windows Server 2012 R2: IUSR
      The 
      Select Users or Groups
       dialog opens.
    2. Locate and select or enter the object name
      • Windows Server 2012 R2: IUSR
    3. Click 
      OK
      . The parent dialog now shows IUSR in the list.
  6. Verify that launch and activation permissions are enabled:
    1. Select IUSR in the top pane.
    2. Verify that the 
      Allow
       check box is selected for all of the listed permissions: Local Launch, Remote Launch, Local Activation, and Remote Activation.
  7. Save your changes and exit:
    1. Click 
      OK
       in the 
      Launch and Activation Permissions
       dialog.
    2. Click 
      OK
       in the nqreporter 
      Properties
       dialog.
    3. Select 
      File
      Exit
       in the 
      Component Services
       window.
      Users who have the proper permissions now can create Custom Reports and Analysis reports without seeing an error.
Scheduled Reports on Linux Harvesters
On Linux Harvesters that are involved in scheduled reports, you might notice memory growth over time with repeated execution of reports. If this memory growth becomes problematic, you can schedule a custom storage engine restart via crontab. The following command needs to be run as root in crontab:
/etc/init.d/nfa_mysqlCSE restart
Note that restarting the custom storage engine will NOT impact data integrity. The only impact would be on any reports that are scheduled to run at the time of the restart.
Polling
Manually Updating Polling When Changing SNMP Profiles
If you add or edit an SNMP profile to correct longstanding polling failures, it can be some time before the affected routers are polled again automatically. If polling has been disabled for some time, we recommend that you manually assign the SNMP profile to the routers and refresh polling as described in the following steps.
Follow these steps:
  1. Make sure that the SNMP profile is set up correctly on the 
    Manage SNMP Profiles
     page (CA PC) or 
    SNMP Profiles List
     page (CA NPC).
  2. Open the 
    Active Interfaces
     page:
    1. Select 
      Administration
       from the NFA console menu. The 
      Administration
       page opens.
    2. Select 
      Interfaces: Physical & Virtual
       from the 
      Administration
       menu.
      The 
      Active Interfaces
       page opens, which lists the current routers and their active interfaces.
  3. Assign the SNMP profile to the routers:
    1. Select the affected routers in the 
      Active Interfaces
       list.
    2. Click 
      Edit
      . The 
      Edit Routers
       dialog opens.
    3. Select the appropriate profile from the 
      SNMP Profile
       list.
    4. Click 
      Save
      . Your setting is saved for each one of the selected routers. The 
      Edit Routers
       dialog closes.
  4. Refresh the polling for the routers manually:
    1. Select 
      System
      Enable Interfaces
       from the menu on the 
      Administration
       page. The 
      Available Interfaces
       page opens.
    2. Click the 
      Refresh
       icon (circular arrow) on the row for each router that has a newly assigned SNMP profile.
      Network Flow Analysis
       attempts to poll the router, then a message opens, which informs you about the success or failure of the polling attempt. Each 
      Refresh
       icon that you clicked appears dimmed to show that the Refresh operation has been performed.
Anomaly Detector
LaunchAnywhere Error During Upgrade
When upgrading Anomaly Detector from any version prior to 9.3.6 to 9.3.6 or later, you might see this error:
Could not find a valid Java virtual machine to load.
You may need to reinstall a supported Java virtual machine.
Workaround:
Click 
OK
 to let the installer continue. This error message can be safely ignored.
Anomaly Detector Will Not Send syslog Alerts
If the Anomaly Detector system is unable to resolve the syslog target server IP to hostname, no syslog alerts will be sent from Anomaly Detector.
Ensure that if the syslog target system is specified as the IP address in the 
Target
 field of 
Alert Targets
, it can be resolved to hostname or fully qualified domain name. If this cannot be set up in DNS, then the hosts file on the Anomaly Detector can be used as a workaround.
User Interface Localization
Decimal Value for Regional Setting
The Regional Settings must use a period (.) to indicate a decimal value. If your deployment is localized to French, use the following steps to customize the decimal symbol value. The steps apply to a Windows Server 2012 R2 system.
Follow these steps:
  1. Log in to the installation server as a user with administrator privileges.
  2. Select 
    Start
    Control Panel
    .
  3. Click the 
    Region and Language
     icon in the 
    Control Panel
    . The 
    Region and Language
     window opens.
  4. Click 
    Additional Settings
    . The 
    Customize Format
     dialog opens.
  5. If the 
    Decimal Symbol
     value is set to a comma (,), select the period (.) from the drop-down list.
    If the
    Format
    value in the
    Region and Language
    window is set to French (France), the default setting for the
    Decimal Symbol
    is a comma.
  6. Save your changes and exit:
    1. Click 
      OK
       in the 
      Customize Format
       dialog.
    2. Click 
      OK
       in the 
      Region and Language
       window.
    3. Close the 
      Control Panel
      .