fast-failover
  
  
    
      Configures fast-failover support on the L2TPv3 tunnel. When configured,
        devices, using this profile, send tunnel requests to both peers, and in turn, establish
        tunnels with both peers. If not configured, tunnel establishment occurs on one peer, with
        failover and other functionality the same as legacy behavior. In case fast failover is
        configured when an active tunnel, with one peer, already exists, the tunnel establishment
        process is re-initiated with both peers. Of the two tunnels established, one is marked
        active while the other is standby. The sessions and routes from the active tunnel are only
        pushed to the dataplane, resulting in creation of data sessions. However, if the active
        tunnel fails, sessions and routes from the standby tunnel are pushed to the dataplane
        thereby providing almost immediate fail over. Both tunnels individually perform connection
        health checkups through hello intervals. This option is disabled by default.
     
    Supported in the following platforms: 
         
         
            - Access Points — AP7502, AP7522,
               AP7532, AP7562, AP7602, AP7612, AP7622, AP7632, AP7662, AP8163, AP8432, AP8533
 
            - Wireless Controller — RFS4010
 
            - Service Platforms — NX5500, NX7500,
               NX9500, NX9600, VX9000
 
         
       
    Syntax
      
      fast-failover {aggressive}
     
    Parameters
      
      fast-failover {aggressive}
      
          
          
          
            
              | fast-failover | 
              Configures fast-failover support on the L2TPv3
                tunnel | 
             
            
              | aggressive | 
              Optional. When enabled, tunnel initiation hello requests
                are set to zero. For failure detections, hello attempts are not retried, regardless
                of the number of retry attempts configured. This option is disabled by
                  default.Note: The hello-interval and retry-attempts parameters are defined in the
                  L2TPv3 Policy context. For more information on configuring an L2TPv3 policy, see
                     l2tpv3-policy-commands. For more information on
                  associating an L2TPv3 policy to an L2TPv3 tunnel, see  use.  
 | 
             
          
         
 | 
     
    Examples
      
      nx9500-6C8809(config-profile testNX9500-l2tpv3-tunnel-TestTunnel2)#show context
include-factory | include fast-failover
  no fast-failover
nx9500-6C8809(config-profile testNX9500-l2tpv3-tunnel-TestTunnel2)#
      nx9500-6C8809(config-profile testNX9500-l2tpv3-tunnel-TestTunnel2)#fast-failover
 aggressive
      nx9500-6C8809(config-profile testNX9500-l2tpv3-tunnel-TestTunnel2)#show context
 l2tpv3 tunnel TestTunnel2
  fast-failover aggressive
nx9500-6C8809(config-profile testNX9500-l2tpv3-tunnel-TestTunnel2)#