Wired Networks

Configuration/Debugging Route Monitoring in MAS

Aruba Employee

Environment : The article applies to AOS running 7.4.0.0 and above 

 

Feature Notes : By default Route Monitoring is disabled on the Mobility Access Switch

 

 

 

Introduction :

 

 

 

In a branch deployments need to detect L3 failure when L2 is still up; dynamic routes are taken care by the respective protocols and 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.

 

 

ISP1 is preferred network

 

 

 

As along as ISP1 is ‘Up’ use ISP1

 

 

 

When ISP1 is ‘Down’ switch to ISP2

 

 

 

If ISP1 is up again switch back ISP2
 
Network Topology :
 
rtaImage.jpg
 
Configuration Steps:
 
Enabling Route Monitoring:
 
You can enable Route Monitoring on the Mobility Access switch using the following steps in the CLI:

Configure a probe profile 
Apply the profile to the uplink VLAN interface. 
 
Note:
 
  • You can associate only one probe-profile per VLAN interface. 
  • You can associate the same probe-profile for multiple VLAN interfaces. 
  • You can configure up to four probe-profiles on the Mobility Access Switch. 
  • You can configure up to two IP addresses and two ulr’s in a probe-profile. 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. 

 
i.e.. 
 
Configure a probe profile
 
(host) (config) #probe-profile L3Monitoring 
(host) (probe profile "L3Monitoring") #destination 10.1.10.1 
(host) (probe profile "L3Monitoring") #pkt-found-cnt 16 
(host) (probe profile "L3Monitoring") #pkt-lost-cnt 16 
(host) (probe profile "L3Monitoring") #pkt-send-freq 11 
(host) (probe profile "L3Monitoring") #protocol icmp 
 

Apply the profile to the uplink VLAN interface
 
(host) (config) # interface vlan 10 
(host) (vlan “10") # probe-profile L3Monitoring 


 
Mobility Access Switch allows to configure multiple default gateways using the metrics option introduced in the CLI. The multiple default gateways can be configured in two different ways: 
 
When DHCP import is configured for the default gateway, you can configure the metrics value under the VLAN interface used for the VPN uplinks to support multiple default gateways.
(host) (config) #ip-profile 
(host) (ip-profile) #route 0.0.0.0 0.0.0.0 <next-hop> <metrics>
 
When DHCP import is not configured for the default gateway, you can configure multiple routes with metrics under the IP profile to support multiple default gateways.
(host) (ip-profile) #default-gateway import dhcp 
(host) (ip-profile) #exit 
(host) (config) #interface vlan <id> 
(host) (vlan "<id>") #metric <cost>
 
ECMP is not supported in the 7.4.0.0 release. In case of metric are same for two default-routes one with least ip address is installed in the routing table 
 
 
i,e..
 
The following example configures multiple default gateways under the IP profile as static routes: 
 
(host) (config) #ip-profile 
(host) (ip-profile) #route 0.0.0.0 0.0.0.0 200.36.36.36 10 
(host) (ip-profile) #route 0.0.0.0 0.0.0.0 142.42.42.42 10 
 
 
The following example configures multiple default gateways under the VLAN interface when the default gateway is obtained from DHCP: 
 
(host) (config) #ip-profile 
(host) (ip-profile) #default-gateway import dhcp 
(host) (ip-profile) #exit 
(host) (config) #interface vlan 10 
(host) (vlan "10") #metric 10 

 
probe-profile L3Monitoring
 
destination <server1 ip-address>
destination <server2 ip-address>
 
ip-profile

Default-gateway import dhcp
 
interface vlan 10
description ISP1
ip address dhcp-client
metric 10
probe-profile L3Monitoring
 
interface vlan 20
description ISP2
ip address dhcp-client
metric 20
probe-profile L3Monitoring
 
Troubleshooting :
 
Using show commands for Route Monitoring 
 
Verifying Route Monitoring Configuration 

Use the following command to view the configuration on a probe-profile: 
(host) #show probe-profile L3Monitoring
probe profile "L3Monitoring" (N/A) 
---------------------------------- 
Parameter Value 
--------- ----- 
Destination IP 10.1.10.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 
 
 
Viewing the probe status of the interfaces 
Use the following show commands to check the probe status of the interfaces where the probe profile is attached.
 
 
host) #show probe 
Vlan Server Protocol Port Probe-State Sent Received 
---------------------------------------------------------------- 
1 10.1.10.1 ICMP N/A Up 1045 1034 
 
(host) #show ip interface brief 
Flags: S - Secondary IP address
Probe: U - Up, D - Down, U/O - Up & Own IP, N/A - Not Applicable
Interface                   IP Address / IP Netmask        Admin   Protocol Probe  Flags
vlan 1                         1.1.1.1 / 255.255.255.0     Up      Up       N/A
vlan 10                      10.16.4.1 / 255.255.255.0     Up      Up       U
 
 
(host) #show ip interface vlan 10 
vlan 1 is Up, protocol is Up 
Internet address is 10.16.4.1 /255.255.255.0 
Address is statically configured 
MTU is 1500 
Metric 10 
Probe Name: L3Monitoring, Probe Status: Up 


 
Verifying Default Gateway Configuration (Default gateway and Matric)
 
Use the following command to view the configuration under the IP profile:
 
(host) #show ip-profile 
ip-profile "default" 
-------------------- 
Parameter Value 
--------- ----- 
Default Gateway N/A 
Import DHCP Gateway Disabled controller-ip loopback1 
route 0.0.0.0 0.0.0.0 192.168.1.1 10 
route 0.0.0.0 0.0.0.0 172.168.1.1 20 


 
(host) #show interface vlan 10
 
VLAN10 is administratively Up, Line protocol is Down
Hardware is CPU Interface, Address is 00:1a:1e:08:6d:80
Description: 802.1Q VLAN
Internet address is unassigned
IPV6 link-local address is fe80::1a:1e00:a08:6d80
Global Unicast address(es):
Routing interface is enabled, Forwarding mode is enabled
Directed broadcast is disabled, BCMC Optimization disabled
Encapsulation 802, Loopback not set
Interface index: 50331658
MTU 1500 bytes
Metric 10      <<<<<<<<<<<<<<<<<<<<<
 

Debugging:
 
In the following scenarios the probe status will be immediately marked as ‘Down’ as probes can’t be sent out
IP address is not assigned for the interface where the probe is applied
Protocol is down for the interface.
Destination URL in probe is not resolved
Route is not present for the probe destination.
MAC is not resolved for the route next-hop.
 
For viewing the logs related to ‘route not present’ & ‘MAC not resolved’, enable ‘probe’  flag  
 
(host)(support)#configure t
(host)(config) #traceoptions
(host)(traceoptions) #routing flags probe
 
For viewing the logs related to URL resolution, enable ‘configuration’  flag  
 
(host)(support)#configure t
(host)(config) #traceoptions
(host)(traceoptions) #routing flags configuration
 
Viewing the Logs

(host) #show trace routing
 
i,e,, log for MAC is not resolved for the route next hop

 
Jul 21 07:49:27 [L3MGR_PROBE] probe_icmp_receive: Probe recvmsg received 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 recvmsg received bytes: -1 Errno: 11

 

 

Version history
Revision #:
1 of 1
Last update:
‎11-10-2014 03:21 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
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.