aos-cx & ip-sla poc

Post on 06-Jan-2022

3 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

AOS-CX & IP-SLA POC

ADOLFO BOLIVARMAY 2020

22

Customer Requirements

• Two path:, Active – Standby links

• NQA or IP-SLA must be used to select the path.• Switch detects failure -> Change to standby link automatically. • Automatic fallback to ppal link (when available).

• Dynamic routing cannot be used.

33

Topology

1/1/1

1/1/2

1/1/1

SW1

SW2

SW3

SW4

1/1/2

1/1/21/1/1

192.168.1.5 192.168.2.5

1/1/1

1/1/2

10.10.12.0/30

10.10.13.0/30 10.10.34.0/30

10.10.24.0/30

vrf mgmtSW1: 172.16.0.101SW2: 172.16.0.102SW3: 172.16.0.103SW4: 172.16.0.104PC1: 172.16.0.108PC2: 172.16.0.109

1/1/3 1/1/3Virtual.10.03.0020

44

SW1 configuration

WAN - ppal

WAN - backup

backup routeMain route

Syslog server

55

IP-SLA ppal

1/1/1

SW1

SW2

SW3

SW4

192.168.1.5 192.168.2.5

SW1ip-sla ppal

icmp-echo 10.10.24.2 source 1/1/1 payload-size 400 probe-interval 10 start-test

10.10.24.2

66

Test connectivity between PC1 and PC2 – ppal link

SW1SW2SW4

77

IP-SLA backup

1/1/2

SW1

SW2

SW3

SW4

192.168.1.5 192.168.2.5

SW1ip-sla backup

icmp-echo 10.10.34.2 source 1/1/2 payload-size 400 probe-interval 10start-test

10.10.34.2

88

Test connectivity between PC1 and PC2 – backup link

Manual config change to backup link

SW1SW3SW4

99

IP-SLA LAN2LAN

SW1

SW2

SW3

SW4

192.168.1.5 192.168.2.5

SW1ip-sla LAN2LAN

icmp-echo 192.168.2.1 source 1/1/3 payload-size 400 probe-interval 10 start-test

192.168.2.11/1/3

1010

IP-SLA Guidelines – AOS CX v10.4

- “ArubaOS-CX supports only SLA configuration through CLI and thresholds can be configured using NAE agents using WebUI/REST.”

- “ArubaOS-CX supports only forever test.”

- “NAE agents must be triggered for each IP-SLA test on every switch.”

- “Predefined actions are action functions that are built in to the Aruba Network Analytics Engine framework. These functions enable the agents of a script to:

- Execute CLI commands in the ArubaOS-CX network operating system ().- Send messages to the system log.”

1111

Install the conectivity_monitor script

12

LAN2LAN IP-SLA Agent

13

LAN2LAN IP-SLA Agent

14

WAN-Backup IP-SLA Agent

15

WAN-Backup IP-SLA Agent

1616

Download the conectivity_monitor script

1717

Edit the conectivity_monitor script, rename it

New name

1818

Edit the conectivity_monitor script, save it

When alert is removed, enter the static IP route

When alert changes to critical, remove the static IP route

19

Click to upload a script

20

Select the script

21

Click on “upload”

22

23

WAN-PPAL IP-SLA Agent

24

WAN-PPAL IP-SLA Agent

25

26

Test configuration

27

SW2: int 1/1/1 shutdownppal link failure

28Config change applied

Backup link being used

29

SW2: int 1/1/1 no shutdownppal link up

30

Main link being usedConfig change applied

31

Syslogs collected

32

References

- https://community.hpe.com/t5/comware-based/policy-based-routing-with-tracking-nqa/td-p/7008226#.XrnmKhNKjq0

- conectivity_monitor v1.1 https://ase.arubanetworks.com/solutions/id/247

- ArubaOS-CX 10.04 Monitoring Guide 8320, 8325 Switch Series.

- ArubaOS-CX 10.04 Network Analytics Engine Guide6200, 6300, 6400, 8320, 8325, 8400 Switch Series

33

Thanks!

top related