No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

LPUF-20-B doesn't support L3VPN causes ping failure

Publication Date:  2014-11-05 Views:  41 Downloads:  0
Issue Description

Topology:

NE40E(R1-R6) use loopback10 binding to nms VPN, Topology is as follows:

 

Description:

After all the configuration is completed,R1&R2 fail to ping R3~R6 through VPN nms,R3~R6 can't ping R1 and R2 through VPN nms either.but it works between R3~R6 themselves.

Create a new sub-interface and binding it to one VPN on CX600, it could not ping any device which directly connected in the VPN instance.

Handling Process

1. Perform ping operations: It's failed;

[tvr-Staritsa-CX600-20.1]ping -vpn nms 10.10.11.1

PING 10.10.11.1: 56 data bytes, press CTRL_C to break

Request time out

Request time out

Request time out

Request time out

Request time out

--- 10.10.11.1 ping statistics ---

5 packet(s) transmitted

0 packet(s) received 100.00% packet loss

 

2. Check FIB table, findings are correct, FIB table checking methods are as follows:

[tvr-Staritsa-CX600-20.1]dis fib vpn-instance nms 10.10.11.1 verbose

Route Entry Count: 1

Destination: 10.10.11.0 Mask : 255.255.255.0

Nexthop : 172.31.122.11 OutIf : Vlanif2513

LocalAddr : 172.31.248.54 LocalMask: 0.0.0.0

Flags : DGU Age : 429644sec

ATIndex : 0 Slot : 0

LspFwdFlag : 1 LspToken : 0x82E2

InLabel : 75776 OriginAs : 0

BGPNextHop : 172.31.122.11 PeerAs : 0

QosInfo : 0x0 OriginQos: 0x0

NexthopBak : 0.0.0.0 OutIfBak : [No Intf]

LspTokenBak: 0x0 InLabelBak : NULL

LspToken_ForInLabelBak : 0x0

EntryRefCount : 0

rt_ulVlanId : 0x0

3. Check ARP table, it's also correct, searching methods are as follows:

[tvr-Staritsa-CX600-20.1]dis arp vlan 2513 int g1/0/0

IP ADDRESS MAC ADDRESS EXPIRE(M) TYPE INTERFACE VPN-INSTANCE VLAN/CEVLAN PVC

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

172.31.248.53 0018-826f-c344 19 D-1 GE1/0/0 2513/-

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

Total:1 Dynamic:1 Static:0 Interface:0

4. Because of having background flow, we cannot judge sending and receiving ping packets situation.keep on checking Vlanif configuration, no anomaly.

 

[tvr-Staritsa-CX600-20.1]dis vlan 2513

VLAN ID Type Status MAC Learning Broadcast/Multicast/Unicast Property

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

2513 common enable enable forward forward forward default

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

Tagged Port: GigabitEthernet1/0/0

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

Interface Physical

GigabitEthernet1/0/0 UP

5 Ping real address of the port without VPN: the IP address is pingable.

[tvr-Staritsa-CX600-20.1]ping 172.31.248.53

PING 172.31.248.53: 56 data bytes, press CTRL_C to break

Reply from 172.31.248.53: bytes=56 Sequence=1 ttl=255 time=7 ms

Reply from 172.31.248.53: bytes=56 Sequence=2 ttl=255 time=2 ms

Reply from 172.31.248.53: bytes=56 Sequence=3 ttl=255 time=2 ms

Reply from 172.31.248.53: bytes=56 Sequence=4 ttl=255 time=2 ms

Reply from 172.31.248.53: bytes=56 Sequence=5 ttl=255 time=1 ms

--- 172.31.248.53 ping statistics ---

5 packet(s) transmitted

5 packet(s) received

0.00% packet loss

round-trip min/avg/max = 1/2/7 ms

6. Check the LPU type on both device: they're Line Processing Unit F-20-B and these boards don't support L3VPN

<tvr-Staritsa-CX600-20.1>dis dev 1

LPU1's detail information:

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

Description: Line Processing Unit F-20-B

Board status: Normal

Register: Registered

Uptime: 2009/04/06 19:52:14

CPU Utilization(%): 13%

<CX600-37.1>dis dev 1

LPU1's detail information:

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

Description: Line Processing Unit F-20-B

Board status: Normal

Register: Registered

The root cause has been positioning, it's LPUF-20-B which does not support L3VPN.

Root Cause

LPUF-20-B doesn't support L3VPN, it needs to purchase GTL license.

Solution
Change board or upgrade LPUF-20-B to LPUF-20-A(need to buy GTL license).
Suggestions
To use L3VPN, Pay attention to LPU type and preferentially checking.

END