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

The newly created sub-interface and ipv4 address sometime can't ping sometime can ping

Publication Date:  2018-01-31 Views:  26 Downloads:  0
Issue Description


The customer's network topology: NE40E --  S7700


Configuration on NE40E:
#
interface Eth-Trunk4.2222
 vlan-type dot1q 2222
 ip address 10.20.30.1 255.255.255.0
#


Configuration on S7700:
#   
vlan batch 419 to 420 600 607 741 1236 to 1248 1300 2222 2739 3113 to 3116 3600
#
interface Vlanif2222
 ip address 10.20.30.2 255.255.255.0
#                                    
interface Eth-Trunk4
 port hybrid tagged vlan 400 419 to 420 600 607 741 1300 2222 2739 3113 to 3114 3116
 port hybrid tagged vlan 4090 to 4091
 mode lacp
#

Alarm Information

 

=============================================================
  ===============display alarm all history===============
=============================================================
----------------------------------------------------------------------------
Index  Level      Date      Time                        Info

3      Critical   17-12-20  05:45:58    The hardware resource(TABLE ID=33,TABL
                                        E NAME=FIBv4) storage media of LPU2(En
                                        tity) exceeded the prealarm threshold[
                                        BasCode:0x12602,EntCode:0x0]
4      Critical   17-12-20  05:45:58    The hardware resource(TABLE ID=33,TABL
                                        E NAME=FIBv4) storage media of LPU1(En
                                        tity) exceeded the prealarm threshold[
                                        BasCode:0x12602,EntCode:0x0]

 

Handling Process

 

1) Check the ping from NE40E to S7700, ping is failed, capture the packets on the outbound and inbound of Eth-Trunk4.2222 on NE40E.
5 ICMP request packets are captured on the outbound of Eth-Trunk4.2222.


5 ICMP reply packets are captured on the inbound of Eth-Trunk4.2222.

2) Do the ping from NE40E to S7700 again, ping is failed, capture the packets on the outbound Eth-Trunk4 on NE40E.
Two types of ICMP packets are capture on the outbound of Eth-Trunk4: 5 ICMP request packets and 5 ICMP reply packets, which is hard to understand

3) Check the alarm history, FIBv4 exceeded the prealarm threshold is observed, the total fib is 673746, according to R&D the fib limit is 512K with the current Paf file.
=============================================================
  ===============display alarm all history===============
=============================================================
----------------------------------------------------------------------------
Index  Level      Date      Time                        Info

3      Critical   17-12-20  05:45:58    The hardware resource(TABLE ID=33,TABL
                                        E NAME=FIBv4) storage media of LPU2(En
                                        tity) exceeded the prealarm threshold[
                                        BasCode:0x12602,EntCode:0x0]
4      Critical   17-12-20  05:45:58    The hardware resource(TABLE ID=33,TABL
                                        E NAME=FIBv4) storage media of LPU1(En
                                        tity) exceeded the prealarm threshold[
                                        BasCode:0x12602,EntCode:0x0]
          
==========================================================
  ===============display fib statistics===============
==========================================================
Route Entry Count : 673746
Route Prefix Count : 673746

 

Root Cause

The fib table has exceeded the limit of 512K.

Solution

The solution is to configure BGP aggregation/summary to reduce the quantity of routes, or upgrade the Paf file to get more fib resource.

END