Developer

Cheers

Customer has asked me to demonstrate that our AOS-CX switches can replace a legacy switching solution that has NQA functionality configured to decide which of the two routes (active - standby) should route traffic. Important to note, Customer does not use dynamic routing protocols.

Reading the AOS-CX monitoring and NAE guides I concluded the same functionality that NQA delivers can be achieved by combining the functionality of IP-SLA with a NAE script (conectivity_monitor v1.1).

The way to demo to Customer was this way:

1. Virtual test environment setup using the AOS-CX OVA (Virtual.10.03.0020). 
2. IP-SLA configuration. 
3. Configuration of Agents and setup of the monitoring dashboard: 

The result of the demo was successful, combining IP-SLA and NAE I was able to demonstrate a routing policy based on the availability of the main - backup links.

4. Syslogs collected: 

This is the video of the PoC result. Attached you will find a pdf with all the details.

Thanks,

Adolfo

Solution for CX6200 and CX6300 switches ??

Hello this is exactly what I need (dual ISP failover) but does anyone have a NAE script (or a suitable solution) that works on a Aruba CX 6200 and CX 6300?? 

Neither of those switches will upload the 'connectivity_monitor' script and I can't figure out what commands are causing the issue.
Or if anyone has solved this another way ?

Many thanks

Peter

Cheers

Customer has asked me to demonstrate that our AOS-CX switches can replace a legacy switching solution that has NQA functionality configured to decide which of the two routes (active - standby) should route traffic. Important to note, Customer does not use dynamic routing protocols.

Reading the AOS-CX monitoring and NAE guides I concluded the same functionality that NQA delivers can be achieved by combining the functionality of IP-SLA with a NAE script (conectivity_monitor v1.1).

The way to demo to Customer was this way:

1. Virtual test environment setup using the AOS-CX OVA (Virtual.10.03.0020). 
2. IP-SLA configuration. 
3. Configuration of Agents and setup of the monitoring dashboard: 

The result of the demo was successful, combining IP-SLA and NAE I was able to demonstrate a routing policy based on the availability of the main - backup links.

4. Syslogs collected: 

This is the video of the PoC result. Attached you will find a pdf with all the details.

Thanks,

Adolfo

Hi, I need the same solution for CX6200, did you get the NAE script for CX6200/6300? 

Thanks!

Solution for CX6200 and CX6300 switches ??

Hello this is exactly what I need (dual ISP failover) but does anyone have a NAE script (or a suitable solution) that works on a Aruba CX 6200 and CX 6300?? 

Neither of those switches will upload the 'connectivity_monitor' script and I can't figure out what commands are causing the issue.
Or if anyone has solved this another way ?

Many thanks

Peter

Cheers

Customer has asked me to demonstrate that our AOS-CX switches can replace a legacy switching solution that has NQA functionality configured to decide which of the two routes (active - standby) should route traffic. Important to note, Customer does not use dynamic routing protocols.

Reading the AOS-CX monitoring and NAE guides I concluded the same functionality that NQA delivers can be achieved by combining the functionality of IP-SLA with a NAE script (conectivity_monitor v1.1).

The way to demo to Customer was this way:

1. Virtual test environment setup using the AOS-CX OVA (Virtual.10.03.0020). 
2. IP-SLA configuration. 
3. Configuration of Agents and setup of the monitoring dashboard: 

The result of the demo was successful, combining IP-SLA and NAE I was able to demonstrate a routing policy based on the availability of the main - backup links.

4. Syslogs collected: 

This is the video of the PoC result. Attached you will find a pdf with all the details.

Thanks,

Adolfo

Not yet but .....!!! Aruba/HPE Tech support are investigating it for me.
I have an open ticket with them and they advised that they tried to test the script but could not even get it to load on an 83xx Switch so ....
I'm keeping my fingers crossed they might yet come up with a solution ... or something :)

Hi, I need the same solution for CX6200, did you get the NAE script for CX6200/6300? 

Thanks!

Solution for CX6200 and CX6300 switches ??

Hello this is exactly what I need (dual ISP failover) but does anyone have a NAE script (or a suitable solution) that works on a Aruba CX 6200 and CX 6300?? 

Neither of those switches will upload the 'connectivity_monitor' script and I can't figure out what commands are causing the issue.
Or if anyone has solved this another way ?

Many thanks

Peter

Cheers

Customer has asked me to demonstrate that our AOS-CX switches can replace a legacy switching solution that has NQA functionality configured to decide which of the two routes (active - standby) should route traffic. Important to note, Customer does not use dynamic routing protocols.

Reading the AOS-CX monitoring and NAE guides I concluded the same functionality that NQA delivers can be achieved by combining the functionality of IP-SLA with a NAE script (conectivity_monitor v1.1).

The way to demo to Customer was this way:

1. Virtual test environment setup using the AOS-CX OVA (Virtual.10.03.0020). 
2. IP-SLA configuration. 
3. Configuration of Agents and setup of the monitoring dashboard: 

The result of the demo was successful, combining IP-SLA and NAE I was able to demonstrate a routing policy based on the availability of the main - backup links.

4. Syslogs collected: 

This is the video of the PoC result. Attached you will find a pdf with all the details.

Thanks,

Adolfo

Hi, I need the same solution for CX6200, did you get the NAE script for CX6200/6300? 

Thanks!

Original Message:
Sent: Jun 11, 2025 09:10 AM
From: killorp
Subject: NQA on AOS-CX? IP-SLA plus NAE script is the answer

Solution for CX6200 and CX6300 switches ??

Hello this is exactly what I need (dual ISP failover) but does anyone have a NAE script (or a suitable solution) that works on a Aruba CX 6200 and CX 6300?? 

Neither of those switches will upload the 'connectivity_monitor' script and I can't figure out what commands are causing the issue.
Or if anyone has solved this another way ?

Many thanks

Peter

Original Message:
Sent: May 21, 2020 12:17 PM
From: AdolfoBolivar
Subject: NQA on AOS-CX? IP-SLA plus NAE script is the answer

Cheers

Customer has asked me to demonstrate that our AOS-CX switches can replace a legacy switching solution that has NQA functionality configured to decide which of the two routes (active - standby) should route traffic. Important to note, Customer does not use dynamic routing protocols.

Reading the AOS-CX monitoring and NAE guides I concluded the same functionality that NQA delivers can be achieved by combining the functionality of IP-SLA with a NAE script (conectivity_monitor v1.1).

The way to demo to Customer was this way:

1. Virtual test environment setup using the AOS-CX OVA (Virtual.10.03.0020). 
2. IP-SLA configuration. 
3. Configuration of Agents and setup of the monitoring dashboard: 

The result of the demo was successful, combining IP-SLA and NAE I was able to demonstrate a routing policy based on the availability of the main - backup links.

4. Syslogs collected: 

This is the video of the PoC result. Attached you will find a pdf with all the details.

(view in My Videos)

Thanks,

Adolfo

Cheers

Customer has asked me to demonstrate that our AOS-CX switches can replace a legacy switching solution that has NQA functionality configured to decide which of the two routes (active - standby) should route traffic. Important to note, Customer does not use dynamic routing protocols.

Reading the AOS-CX monitoring and NAE guides I concluded the same functionality that NQA delivers can be achieved by combining the functionality of IP-SLA with a NAE script (conectivity_monitor v1.1).

The way to demo to Customer was this way:

1. Virtual test environment setup using the AOS-CX OVA (Virtual.10.03.0020). 
2. IP-SLA configuration. 
3. Configuration of Agents and setup of the monitoring dashboard: 

The result of the demo was successful, combining IP-SLA and NAE I was able to demonstrate a routing policy based on the availability of the main - backup links.

4. Syslogs collected: 

This is the video of the PoC result. Attached you will find a pdf with all the details.

Thanks,

Adolfo

Do you have look / ask https://github.com/aruba/nae-scripts/ ?

Cheers

Customer has asked me to demonstrate that our AOS-CX switches can replace a legacy switching solution that has NQA functionality configured to decide which of the two routes (active - standby) should route traffic. Important to note, Customer does not use dynamic routing protocols.

Reading the AOS-CX monitoring and NAE guides I concluded the same functionality that NQA delivers can be achieved by combining the functionality of IP-SLA with a NAE script (conectivity_monitor v1.1).

The way to demo to Customer was this way:

1. Virtual test environment setup using the AOS-CX OVA (Virtual.10.03.0020). 
2. IP-SLA configuration. 
3. Configuration of Agents and setup of the monitoring dashboard: 

The result of the demo was successful, combining IP-SLA and NAE I was able to demonstrate a routing policy based on the availability of the main - backup links.

4. Syslogs collected: 

This is the video of the PoC result. Attached you will find a pdf with all the details.

Thanks,

Adolfo

Do you have look / ask https://github.com/aruba/nae-scripts/ ?

Cheers

Customer has asked me to demonstrate that our AOS-CX switches can replace a legacy switching solution that has NQA functionality configured to decide which of the two routes (active - standby) should route traffic. Important to note, Customer does not use dynamic routing protocols.

Reading the AOS-CX monitoring and NAE guides I concluded the same functionality that NQA delivers can be achieved by combining the functionality of IP-SLA with a NAE script (conectivity_monitor v1.1).

The way to demo to Customer was this way:

1. Virtual test environment setup using the AOS-CX OVA (Virtual.10.03.0020). 
2. IP-SLA configuration. 
3. Configuration of Agents and setup of the monitoring dashboard: 

The result of the demo was successful, combining IP-SLA and NAE I was able to demonstrate a routing policy based on the availability of the main - backup links.

4. Syslogs collected: 

This is the video of the PoC result. Attached you will find a pdf with all the details.

Thanks,

Adolfo

You can ask on Github issue... 

Do you have look / ask https://github.com/aruba/nae-scripts/ ?

Cheers

Customer has asked me to demonstrate that our AOS-CX switches can replace a legacy switching solution that has NQA functionality configured to decide which of the two routes (active - standby) should route traffic. Important to note, Customer does not use dynamic routing protocols.

Reading the AOS-CX monitoring and NAE guides I concluded the same functionality that NQA delivers can be achieved by combining the functionality of IP-SLA with a NAE script (conectivity_monitor v1.1).

The way to demo to Customer was this way:

1. Virtual test environment setup using the AOS-CX OVA (Virtual.10.03.0020). 
2. IP-SLA configuration. 
3. Configuration of Agents and setup of the monitoring dashboard: 

The result of the demo was successful, combining IP-SLA and NAE I was able to demonstrate a routing policy based on the availability of the main - backup links.

4. Syslogs collected: 

This is the video of the PoC result. Attached you will find a pdf with all the details.

Thanks,

Adolfo