CA NFA Console and Harvester HA

[Legacy User]

Hi,

 

We are Using CA NFA 9.5.0

 

We want to know how we will set up HA Higher Availability for CA NFA Console and for Harvester.

 

Is it possible?

 

Please let me know it's an important requirement from customer side, i didn't find any document for this, if it is available please share with us. 

[Christopher Walsh]

NFA doesn't currently have a high availability solution. 

[Legacy User]

Hey Chris,

 

Thank you very much for your swift response. we will update the same to customer

[Imran Badruddin]

Hi,

We have similiar issue as per Dharmender. I was thinking what if we to configure the routers to send flow data to two harvesters? Harvester A connects to Console A and Harvester B connects to Console B? Is this possible? What is the impact on the router resources?

[Christopher Pearson]

If you want to send netflow to two discrete NFA installations that is fine. There would be more load on the source object. That would be difficult for us to determine, and would be a question of the device manufacture, and or your internal testing. It should be noted that you would not want to send to two harvesters under the same NFA system (configured to talk to the same NFA console).

[Alex Yasuda]

To have the same flows in 2 Different Harvesters you can use the old procedure as a reference is:

How to forward flows to an external server from the Harvester (Flow Cloning).

You must be running ReporterAnalyzer 7.3 (and Harvester 4.3) or higher to enable this feature.

To forward flows from the Harvester to an external server, follow these steps:

• First, create the file FlowCloneDef.ini in D:\NetQoS\Netflow\bin.
  
  
  • The first line of the INI file must either be:
    
    /use defaults; take default setup
    (use first available NIC to send flows on UDP 9995)
    
    OR
    
    /port=9994;
    (Use and change this to modify the port flow data is exported on ... /port= must be on the first line of the .ini file)
    
    
  • The subsequent lines should contain the destinations:
    
    /dest ip=192.168.0.146 ; send cloned packets to 192.168.0.146
    /dest ip=192.168.0.144 ; send cloned packets to 192.168.0.144
    
    
  • Save the file and close.
    
    
• Next, edit the Harvester database with these commands (in a cmd prompt on the Harvester server):
  
  RA 7.X, 8.X:
  
  mysql -P 3306 harvester
  update parameter_descriptions set defaultvalue='Y' where parameter='EnableFlowCloner';
  exit
  
  RA 9.X:
  
  mysql -P 3308 harvester
  update parameter_descriptions set defaultvalue='Y' where parameter='EnableFlowCloner';
  exit

------------------------------
Technical Support Engineer
Broadcom
------------------------------