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

L3 VPN data forwarding are affected because uplink interface belongs to the LPUF-21 Type B board.

Publication Date:  2012-07-27 Views:  50 Downloads:  0
Issue Description
Customer has following network topology ( see pic 1) There is all necessary routing information about P2P network 10.163.107.136/30 and 10.163.108.136/30. But there is no data forwarding to the network 10.163.107.136 (see ping examples on the pic 1)


                                                                                       Pic 1
Alarm Information
None
Handling Process
Replace TypeB board by TypeA or apply and activate GTL license for TypeB board.


Root Cause
According to configuration, Server Platform is CE connected trough L3 VPN service, so network 10.163.107.136/30 is advertised as BGP vpnv4 network (see pic 2)

                                                                                      Pic 2
From the opposite side (SMR-PE-NE40E-1 and SMR-PE-NE40E-2) we can see the same situation:
*************!!!****************
<SMR-DOC-PE-NE40E-2>disp ip routing-table vpn-instance corp 10.163.103.73
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Table : corp
Summary Count : 1
Destination/Mask    Proto  Pre  Cost       Flags NextHop         Interface
  10.163.103.72/30  BGP    255  0           RD   10.63.0.41      GigabitEthernet1/1/0
<SMR-DOC-PE-NE40E-2>
<SMR-DOC-PE-NE40E-2>ping -vpn-instance corp 10.163.103.73
  PING 10.163.103.73: 56  data bytes, press CTRL_C to break
    Reply from 10.163.103.73: bytes=56 Sequence=1 ttl=254 time=1 ms
    Reply from 10.163.103.73: bytes=56 Sequence=2 ttl=254 time=1 ms
    Reply from 10.163.103.73: bytes=56 Sequence=3 ttl=254 time=1 ms
    Reply from 10.163.103.73: bytes=56 Sequence=4 ttl=254 time=1 ms
    Reply from 10.163.103.73: bytes=56 Sequence=5 ttl=254 time=7 ms
  --- 10.163.103.73 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 1/2/7 ms
<SMR-DOC-PE-NE40E-2>
****************!!!******************
****************!!!******************
<SMR-DOC-PE-NE40E-1>disp ip routing-table vpn-instance corp 10.163.103.73
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Table : corp
Summary Count : 1
Destination/Mask    Proto  Pre  Cost       Flags NextHop         Interface
  10.163.103.72/30  BGP    255  0           RD   10.63.0.41      GigabitEthernet1/0/0
<SMR-DOC-PE-NE40E-1>ping -vpn-instance corp 10.163.103.73               
  PING 10.163.103.73: 56  data bytes, press CTRL_C to break
    Request time out
    Request time out
    Request time out
    Request time out
    Request time out
  --- 10.163.103.73 ping statistics ---
    5 packet(s) transmitted
    0 packet(s) received
    100.00% packet loss
<SMR-DOC-PE-NE40E-1>
During analysis process we found that on the SMR-DOC-PE-NE40E-1 router, outgoing interface GigabitEthernet 1/0/0 belongs to the LPUF-21-TypeB board (problem network 10.163.107.136/30 is advertised by this device)
At the same time on the SMR-DOC-PE-NE40E-2 router, outgoing interface GigabitEthernet 1/1/0 belongs to the LPUF-21-TypeA board (reachable network 10.163.108.136/30 is advertised by this device)
According to documentation LPUF-21-TypeB  board doesn’t support following service: L3VPN, MVPN, IPv6. When LPUF-21-TypeB board is used on the router, information in Control Plane are exchanged free (that is why routing information about net 10.163.107.136/30 exists on the all PE devices), but information in Forwarding Plane of device is restricted (FIB doesn’t contain appropriate records how to reach network 10.163.107.136/30. That is why there is no data forwarding to network 10.163.107.136/30)
You have to expand TypeB board by using GTL license or replace it by TypeA board.
Using LPUF-21-TypeB board in up-link direction to the MPLS BackBone is root cause of this problem situation. We shouldn’t use TypeB board(without GTL license) if there is L3VPN service on the router.

Suggestions
TypeB board should be used on the routers without L3VPN, MVPN services (for example on the P device, but not PE)

END