Reset Search
 

 

Article

WiNG Failed to establish L2TPv3 tunnel

« Go Back

Information

 
TitleWiNG Failed to establish L2TPv3 tunnel
Symptoms
Failed to established L2TPv2 tunnel
Environment
  • NX5500
  • AP7522
  • WiNG 5.8.5
Cause
Peer 1 and Peer 2 IP address are not accessible from the AP.
 
l2tpv3 tunnel VLAN999
  peer 1 ip-address 10.0.255.251 hostname NX5500-Primary router-id any 
  peer 2 ip-address 10.0.255.252 hostname NX5500-Backup router-id any 
  use l2tpv3-policy Default
  session VLAN999 pseudowire-id 1 traffic-source vlan 999
  establishment-criteria rf-domain-manager
 l2tpv3 inter-tunnel-bridging

 
Resolution
Reconfigure the IP address that the AP used for adoption

IP address that is using for Adoption
controller host 172.20.50.100 pool 1 level 2
controller host 172.20.50.101 pool 1 level 2

Reconfigure the L2TPv3 configuration
 
l2tpv3 tunnel VLAN999
  peer 1 ip-address 172.20.50.100 router-id any 
  peer 2 ip-address 172.20.50.101 router-id any 
  use l2tpv3-policy Default
  session VLAN999 pseudowire-id 1 traffic-source vlan 999
  establishment-criteria rf-domain-manager
 l2tpv3 inter-tunnel-bridging

 
Additional notes
Use command to check the L2TPv3 tunnel,
 
WLC~#show l2tpv3 tunnel-summary
--------------------------------------------------------------------------------------------------------------------------
Sl No  Tunnel Name                                      Peer  Tunnel State                     Tunnel Mode  Estd/Total Sessions   Encapsulation Proto
-------------------------------------------------------------------------------------------------------------------------
 1     l2tpv3-tunnel-1-ap7532-15E8B0-0.0.0.0            1     Established                      Active            1/1              IP
--------------------------------------------------------------------------------------------------------------------------

​

 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255