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

Ping Fails Because the LPUF-20-B on an NE40 Does not Support L3VPN

Publication Date:  2013-01-07 Views:  55 Downloads:  0
Issue Description

As shown in the following networking, six NE40Es from R1 to R6 use loopback 10 to be bound to the VPN named NMS.

 

After the configuration is complete, R1 and R2 ping R3 to R6 by sending packets carrying NMS VPN tags and the ping operations fail; R3 to R6 ping R1 and R2 by sending packets carrying NMS VPN tags, and the ping operations fail. R3, R4, R5, R6, however, can ping through each other.

On the CX600, a sub-interface is created and bound to the VPN. It is found that the VPN instance fails to ping through any directly connected device.

 

Handling Process

1.         Ping the NMS. The ping fails.

[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 the FIB table on the device. The FIB entries are correct. An example is shown as follows.

[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 the ARP table. The entries are correct. An example is shown 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 traffic of other services, it is hard to check the receiving and sending of ping packets on the interface. Then, check the configurations on the VLANIF interface. The configurations are correct.

[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 the actual IP address of the interface. The ping is successful.

[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                                          

Check the type of the interface boards on the CX600s and find that both CX600s use LPUF-20-Bs. However, an LPUF-20-B does not 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%                                  

<tvr-Goritsy-CX600-37.1>dis dev 1                                              

LPU1's detail information:                                                      

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

  Description:                            Line Processing Unit F-20-B          

  Board status:                           Normal                                

  Register:                               Registered                           

The fault occurs because the LPUF-20-Bs do not support L3VPN.

Root Cause

the board don't support the feather.

Solution

Replace the LPUF-20-Bs or upgrade the LPUF-20-Bs to LPUF-20-As (You need to purchase the GTL license).

END