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

Gigabit Ethernet of NE40-NE80 didn't foward the packets

Publication Date:  2012-07-27 Views:  37 Downloads:  0
Issue Description
Gigabit Ethernet of NE40/NE80 didn't foward the packets.
            
Alarm Information
Today we had a window maintenance in order to activate a peering to customer X. Before the maintenance window we prepared the environment, the fibers and put a script on the router. On time scheduled, we migrated the peer. Some adjusts were peformed and NE40/80 start to receive and advertise all BGP routes, exactly as Cisco did. However, we still have to check the load balance and made some tests. During these tests we found some routing problem. Checked the configuration and really right, however some packet that was comming from Intelig Customer it was not being fowarded by NE80, even though NE80 had the necessary route in its routing table. We made a lot of tests and collect a lot of information. The window time was expanded, anyway, near to the end some customers complaint to customer X and customer X decided to abort the intervention.
Handling Process
Command for checking route table mode of LPU
[View]  diagnostic view
[Command] display lpu lpupara [slot-num]
[Example]
[ixrrjo103-diag]display lpu lpupara 1 
 Start to Display Lpu flash parameter of 01... 
[ixrrjo103-diag]
Slot No. 1 Info is:
   LPU Param:
 0.FSU_VERSION : Release version 
 1.FSU_DEBUG_COMM : Debug through serial port 
 2.FSU_NETSTATUS1 : Net1 is online 
 3.FSU_NETSTATUS2 : Net2 is online 
 4.FSU_WATCH_DOG : Watch dog is working 
 5.FSU_NPS_STATICS : NPS collect statistics 
 6.FSU_BUILDRUN : Buildrun is on 
 7.FSU_EPLD0 : EPLD0 is up-to-date 
 8.FSU_EPLD1 : EPLD1 is up-to-date 
 9.FSU_ROUTE_TAB : Small route table 
 10.FSU_RAINIER_VER :   31 
 11.FSU_RULE_MODE : Status of RULE Config Mode is RANGE mode 
 12.FSU_LSP_TAB : Small lsp table 
 13.FSU_PRODUCT_FLAG : NE80 
 14.FSU_24BIT_EXT1 : 0 
 15.FSU_EPOREQ : NONE
Command for setting route table mode of LPU
[View]  diagnostic view
[Command] efu fib {large/small} [slot-num]
[Example]
[ixrrjo103-diag]efu fib ?
  large    Efu large fib 
  small    Efu small fib 
  summary  Efu fib summary 
[ixrrjo103-diag]efu fib large 1 
 Start to Set efu fib mode of 01... 
[ixrrjo103-diag]
Slot No. 1 Info is:
 Set Flash Parameter  Ok !! 
 
[ixrrjo103-diag] 
2 Commands for inquiring FIB on LPU of NE40/NE80
2.1 Command for inquiring all FIB entries on LPU of NE40/NE80
[View]  diagnostic view
[Command] display table [slot-num] 7
[Example]
[ixrrjo103-diag]display table 2 7
 Used Leaf Count : 174019
 Free Leaf Count : 336633
 Free PSCB Count : 358413
 IP=127.0.0.1, prefix=32, Th0=100, Th1=0, Color=0x0,qppb=0x0
 [0] ip=127.0.0.1, hop_action=0x60, tb=0x0, tp=0x0, subindex=0 ,eContext=0
 [1] ip=0.0.0.0, hop_action=0x0, tb=0x0, tp=0x0, subindex=0 ,eContext=0
 [2] ip=0.0.0.0, hop_action=0x0, tb=0x0, tp=0x0, subindex=0 ,eContext=0
 IP=127.255.255.255, prefix=32, Th0=100, Th1=0, Color=0x0,qppb=0x0
 [0] ip=127.0.0.1, hop_action=0x60, tb=0x0, tp=0x29, subindex=0 ,eContext=0
 [1] ip=0.0.0.0, hop_action=0x0, tb=0x0, tp=0x0, subindex=0 ,eContext=0
 [2] ip=0.0.0.0, hop_action=0x0, tb=0x0, tp=0x0, subindex=0 ,eContext=0
 IP=255.255.255.255, prefix=32, Th0=100, Th1=0, Color=0x0,qppb=0x0
 [0] ip=127.0.0.1, hop_action=0x60, tb=0x0, tp=0x29, subindex=0 ,eContext=0
 [1] ip=0.0.0.0, hop_action=0x0, tb=0x0, tp=0x0, subindex=0 ,eContext=0
 [2] ip=0.0.0.0, hop_action=0x0, tb=0x0, tp=0x0, subindex=0 ,eContext=0
 IP=200.184.194.10, prefix=32, Th0=100, Th1=0, Color=0x0,qppb=0x0
 [0] ip=127.0.0.1, hop_action=0x60, tb=0x0, tp=0x0, subindex=0 ,eContext=0
 [1] ip=0.0.0.0, hop_action=0x0, tb=0x0, tp=0x0, subindex=0 ,eContext=0
 [2] ip=0.0.0.0, hop_action=0x0, tb=0x0, tp=0x0, subindex=0 ,eContext=0 
……
Command for inquiring a FIB entries for a specific prefix on LPU of NE40/NE80
[View]  diagnostic view
[Command] display efu fib [slot-num] [prefix] [mask-length]
[Example]
[ixrrjo103-diag]display efu  fib  1 10.111.77.0 24
 Start display lpu fib on board 01...
 Message sending success.
[ixrrjo103-diag]
 IP address              = 10.111.77.0
 IP prefixLength         = 24
 VRF index               = 0
 Signature               = 0
 counterskip             = 1
 cbi                     = 0
 ecmpThr1                = 100
 ecmpThr2                = 0
 qppbindex               = 0x0
          nextHop[0] is REDIRECTION_CP_DEF
          nextHop[0] is REDIRECT SNMP 
      
Root Cause
Sometimes the route that we have on Routing table was not being showed on FIB table.
the router behavior during the maintenance window was correct, as it has the boards (hidden configured to have a small FIB) to discard routes when FIB be full (some routes will be discarded, so no path will be found to some destination).
Suggestions

Use all this command during equipment instalation and before activation on real network to prevent routing problems by a difficult coming from factory.

But when the lpu fib working in "large" model,the forward performance of this lpu will come down.
      

END