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
MENU

Some Services Cannot Be Forwarded Because the Number of Routes Exceeds the FIBv4 Specifications on LPUC of the NE5000E

Publication Date:  2013-09-03 Views:  6 Downloads:  0
Issue Description
1. The attachment describes the networking.
2. NM clients on the core network fail to log in to the NM server.
3. The NE40E fails to ping the IP address 10.1.1.2 of 7609 but can ping the loopback address 1.1.1.11 of 7609.
4. The 7609 cannot ping the loopback address or 10.1.2.2 of NE40E-A.
Handling Process

1. Log in to the NE40E and ping 7609. The NE40E can ping 7609 but cannot ping 10.1.1.2 or 10.1.1.1.
2. Check forwarding entries and routing entries on the NE40E. The entries are normal.
3. Tracert 10.1.1.2 from the NE40E. A loop exists between the two NE5000E devices.
   traceroute to  10.1.1.2(10.1.1.2), max hops: 30 ,packet length: 40
 1 10.164.243.13 2 ms  1 ms  3 ms     
 2 10.164.243.2 2 ms  1 ms  2 ms     
 3 10.164.243.1 3 ms  1 ms  1 ms     
 4 10.164.243.2 1 ms  2 ms  2 ms 
 5 10.164.243.1 2 ms  1 ms  1 ms 

 
4. Log in to NE5000E-A and check routing information. The routing table, forwarding table, and label table are correct.
5. NE5000E-A can use the upstream interface address or loopback address as the source address to ping 10.1.1.2.
6. Run the display alarm all command to check alarms on NE5000E-A. A large number of alarms indicating that the number of routes exceeds the FIBv4 specifications in slots 1, 2, 3, and 4.

<NE5000E-A>disp alarm all
----------------------------------------------------------------------------
Index    Level        Date        Time                  Info      
 
1        Error        10-08-18    06:51:54    The hardware resource(ID=33,Use
                                              r=FIBv4) storage media of LPU4(E
                                              ntity) exceeded the prealarm thr
                                              eshold 
2        Error        10-08-18    06:51:54    The hardware resource(ID=5,User
                                              =FIBv4) storage media of LPU4(En
                                              tity) exceeded the prealarm thre
                                              shold 
3        Error        10-08-18    06:51:54    The hardware resource(ID=33,Use
                                              r=FIBv4) storage media of LPU1(E
                                              ntity) exceeded the prealarm thr
                                              eshold 

7. In the hidden view, run the disp tcam-config slot 1 command on NE5000E-A. The FIBv4 threshold in slot 1 is 340K.
  [NE5000E-A-hidecmd]disp tcam-config slot 1
Configuration mode [ CORE ] :

Configuration [ LPUC_TCAMA ] :
TableName             Capacity   StartAddr   KeyLen   ShareID
ShareCapacity
----------------------------------------------------------------------------
-
FIBV4                 340        0x0         72       5          340   
ARPV4                 20         0x55000     72       6          20    
FIBV6                 18         0x6e800     144      4          18    
ARPV6                 4          0x6c800     144      1          4     
MFIBV4_DUMMY          1          0x68000     144      3          9     
MFIBV6_DUMMY          1          0x78000     288      0          8     
MFIBV4                8          0x68000     144      3          9     
MFIBV6                3          0x78000     288      0          8     
ACLV4                 16         0x60000     144      2          16    
ACLV6                 4          0x78000     288      0          8     
STATIC_EMAC           1          0x5a000     72       8          1     
DYNAMIC_EMAC          23         0x5a400     72       9          23    
FIBV6S                0          0x0         72       7          0   

8. NE5000E-A carries Internet routes on the entire network, which are more than 350K. Run the display elabel command on LPUC to check the threshold of FIBv4 entries. The result is 400K. Change the PAF file and restart NE5000E-A. The problem is solved.
  [NE5000E-A-hidecmd]display tcam-config slot  1                         
Configuration mode [ MANUAL ] :                                                 
Configuration [ LPUC_TCAMA ] :                                                  
TableName             Capacity   StartAddr   KeyLen   ShareID   ShareCapacity   
-----------------------------------------------------------------------------   
FIBV4                 400        0xc000      72       4          400            
ARPV4                 20         0x0         72       1          20             
FIBV6                 0          0x0         144      8          0              
ARPV6                 0          0x0         144      5          0              
MFIBV4_DUMMY          1          0x7c000     144      7          8              
MFIBV6_DUMMY          0          0x0         288      9          0              
MFIBV4                8          0x7c000     144      7          8              
MFIBV6                0          0x0         288      9          0              
ACLV4                 24         0x70000     144      6          24             
ACLV6                 0          0x0         288      9          0              
STATIC_EMAC           1          0x5000      72       2          1              
DYNAMIC_EMAC          27         0x5400      72       3          27             
L2MC_MAC              0          0x5000      72       2          1              
FIBV6S                0          0x0         72       0          0  
Root Cause
The number of IPv4 forwarding entries on LPUs exceeds the specifications.
Solution

1、change the board to LPUE, the specification is 1024K.
2、reduce the route number.

Suggestions

1.  This fault occurs because the number of FIBv4 entries on the NE5000E exceeds the specifications.

2.  NE5000E is deployed at the upper layer and often carries all routes of the entire network. For earlier LPUB/LPUC, notice FIBv4 specifications. Ask the customer to replace the board if necessary.

END