Wired Networks

How to configure Route Monitoring in MAS

Branch deployments need to detect L3 failure when L2 is still up. Dynamic routes are taken care by the respective protocols. Static routes needs a mechanism to detect the L3 failure and update routing table accordingly.

Route Monitoring provides an ability to remove a route based upon probe status.  In addition to basic route monitoring feature, it also brings in multiple default gateway support.

 

Route Monitoring enables the MAS to monitor the L3 uplink status using ping probe.

Ping probe destined to a server IP address is sent on the uplink interface which is under monitoring.

Based on the status of ping reply, probe status of the interface is updated to up or down.

Interface probe status is changed from up to down, when there are consecutive unacknowledged pings.

When the probe status of the interface is down, static routes are removed from the routing table for respective interface

Interface probe status is changed from down to up when there are acknowledged pings.

When the probe status of the interface is up again, network routes are added back  

 

Enabling Route Monitoring :
            Route Monitoring can be enabled on the Mobility Access switch using the following steps in the CLI.
            By default Route Monitoring is disabled on the Mobility Access Switch. 
           Configure a probe profile
           Apply the profile to the uplink VLAN interface.


FYI:

Only one probe-profile can be associated per VLAN interface.
Same probe-profile can be associated with multiple VLAN interfaces.
Up to four probe-profiles can be configured.
Up to two IP addresses can be configured. When there are multiple hosts, probe status of the interface is changed to up if ping succeeds to at least one of the configured hosts.

 

(host) (config) #probe-profile Monitor

(host) (probe profile "Monitor") #destination 10.1.1.1

(host) (probe profile "Monitor") #pkt-found-cnt 16

(host) (probe profile "Monitor") #pkt-lost-cnt 16

(host) (probe profile "Monitor") #pkt-send-freq 11

(host) (probe profile "Monitor") #protocol icmp 



 

(host) (config) # interface vlan 10

(host) (vlan “10") # probe-profile Monitor



 

pkt-found-cnt: Minimum number of ping responses to keep the probe status up

Default:6 Allowed range: 2-32

 

pkt-lost-cnt: Minimum number of packet loss in the ping to mark

the interface probe status as down

Default:6 Allowed range: 2-32

 

pkt-send-freq : Frequency at which ping packets are sent

Default:5 Allowed range: 1-32

 

protocol : Protocol used for the probe operation

 

(host) #show probe-profile L3Monitoring

probe profile "L3Monitoring" (N/A)

----------------------------------

Parameter Value

--------- -----

Destination IP 10.1.1.1

Destination Host Name N/A

Packet Lost Count 16

Packet Found Count 16

Packet Send Frequency (Secs) 11

Protocol icmp

 

Use the following command to view the list of probe-profiles configured and their references:

(host) #show probe-profile

probe profile List

------------------

Name          References  Profile Status

----          ----------  --------------

default       0            N/A

L3Monitoring  1            N/A

test          0            N/A 

 

(host)(support)#configure t
(host)(config) #traceoptions
(host)(traceoptions) #routing flags probe
 



To View the logs:

(host) #show trace routing




Jul 21 07:49:27 [L3MGR_PROBE] probe_icmp_receive: Probe recvmsgreceived bytes: -1 Errno: 11
Jul 21 07:49:27 [L3MGR_PROBE] probe_icmp_send_dest_all vlan_id 500
Jul 21 07:49:27 [L3MGR_PROBE] probe_icmp_send Mac binding is not resolved yet
Jul 21 07:49:27 [L3MGR_PROBE] probe_icmp_send Mac binding is not resolved yet
Jul 21 07:49:27 [L3MGR_PROBE] probe_state_change: ip_resolved[0]: 40.40.40.3 id: 0x0000a1f4 seq: 0x00000000 window: 0x00000000 current: 0x00000000
Jul 21 07:49:27 [L3MGR_PROBE] probe_state_change: ip_resolved[1]: 60.60.60.3 id: 0x0000a1f4 seq: 0x00000000 window: 0x00000000 current: 0x00000000
Jul 21 07:49:32 [L3MGR_PROBE] probe_icmp_receive: Probe recvmsgreceived bytes: -1 Errno: 11

Version history
Revision #:
1 of 1
Last update:
‎04-07-2015 02:23 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.