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

NE40 cannot Ping through 8850 because Outbound Traffic is Close to Bandwidth

Publication Date:  2012-07-27 Views:  37 Downloads:  0
Issue Description
NE4 connects with 8850 through L2 Ethernet port. NE40 cannot ping through any interface address of 8850 and 8850 either cannot ping through any interface address of NE40. Users at 8850 and external network can ping through.
Topology: internet----NE40----8850----user
Software Version: VRP3.10-2321SP02
      
Alarm Information
The interface connecting 8850 with NE40 traffic is as follows:
<NE40_A>disp int ether 2/0/2                                            
  Ethernet2/0/2 current state: up                                               
  Hardware is LAN-FastEthernet,                                                 
  Address is 00e0-fc3a-3b3c                                                     
  Description: to 8850                                                          
  The Maximum Transmit Unit is 1500 bytes, the BandWidth is 100000 Kbits        
  Send-frame-type is Ethernet_II, loopback not set                              
  Negotiation enabled, full-duplex, 100Mbps                                     
  This port works as a Switch                                                   
  Statistics last cleared: never                                                
  Traffic statistics:                                                           
    Last 5 minutes input rate 4654714 bytes/sec, 13685 packets/sec              
    Last 5 minutes output rate 11709922 bytes/sec, 14359 packets/sec            
    33374596408 packets input, 12267142024082 bytes                             
    35868596563 packets output, 26155961314897 bytes                            
   .............................                                   
Handling Process
1. Check configuration and there is no related rules to deny relevant address ping NE40.
2. Ping NE40 from 8850 and debug ip icmp at NE40. It is found that NE40 receives pinged packet from 8850. 
3. Use interconnected port of NE40 and 8850 as mirror and capture packet. During the process ping NE40 from 8850 and ping 8850 from NE40. It cannot capture ICMP packet from NE40.
4. When the response packet from NE40 MPU floods the interface and forwards, it is influenced. Use the commands under system view "flow-path be". Change interface forwarding as "be" , NE40 and 8850 can ping through.
      
Root Cause
The software version of VRP3.10-2321SP02 of NE40 has bug. When outbound traffic is close to bandwidth of the port, packets from MPU will be discarded.
Suggestions
When other device and NE40 connect directly but cannot ping through, check whether outbound traffic is close to bandwidth or not. If it is, configure flow-path be and test.

END