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

Packet Loss Alarms Frequently Occur on the SSP of the NE5000E

Publication Date:  2012-07-27 Views:  47 Downloads:  0
Issue Description
An engineer reported that packet loss information frequently occurred in the log of the SSP of the NE5000E at a site.
Equipment version:
<SSP3000-A>vrbd
Huawei SSP3000 Software
SSP3000 Version V500R003C06B060 
 
Alarm Information
Packet loss alarms are given on each service slot (including the slots of the POS interface and GE interface) of the SSP3000.
Jun 13 19:19:00 2008 IPCTL-ZJM-SSP3000-A FLOWSEC/5/TRAP:1.3.6.1.4.1.2011.25.125.9.2.1 index: 1 There are 018649 packets lost at 0(0:ingress/1:egress) lost type is 192 in 4 slot.
#Jun 13 19:19:00 2008 IPCTL-ZJM-SSP3000-A FLOWSEC/5/TRAP:1.3.6.1.4.1.2011.25.125.9.2.1 index: 0 There are 092 packets lost at 1(0:ingress/1:egress) lost type is 151 in 6 slot.
#Jun 13 19:19:00 2008 IPCTL-ZJM-SSP3000-A FLOWSEC/5/TRAP:1.3.6.1.4.1.2011.25.125.9.2.1 index: 1 There are 090 packets lost at 1(0:ingress/1:egress) lost type is 151 in 6 slot.
#Jun 13 19:19:00 2008 IPCTL-ZJM-SSP3000-A FLOWSEC/5/TRAP:1.3.6.1.4.1.2011.25.125.9.2.1 index: 0 There are 024815 packets lost at 0(0:ingress/1:egress) lost type is 192 in 7 slot.
#Jun 13 19:19:00 2008 IPCTL-ZJM-SSP3000-A FLOWSEC/5/TRAP:1.3.6.1.4.1.2011.25.125.9.2.1 index: 0 There are 092 packets lost at 1(0:ingress/1:egress) lost type is 151 in 7 slot.
#Jun 13 19:19:00 2008 IPCTL-ZJM-SSP3000-A FLOWSEC/5/TRAP:1.3.6.1.4.1.2011.25.125.9.2.1 index: 1 There are 034241 packets lost at 0(0:ingress/1:egress) lost type is 192 in 7 slot.
#Jun 13 19:19:00 2008 IPCTL-ZJM-SSP3000-A FLOWSEC/5/TRAP:1.3.6.1.4.1.2011.25.125.9.2.1 index: 0 There are 053326 packets lost at 0(0:ingress/1:egress) lost type is 192 in 8 slot.
#Jun 13 19:19:00 2008 IPCTL-ZJM-SSP3000-A FLOWSEC/5/TRAP:1.3.6.1.4.1.2011.25.125.9.2.1 index: 0 There are 094 packets lost at 1(0:ingress/1:egress) lost type is 151 in 8 slot.
#Jun 13 19:19:00 2008 IPCTL-ZJM-SSP3000-A FLOWSEC/5/TRAP:1.3.6.1.4.1.2011.25.125.9.2.1 index: 1 There are 012544 packets lost at 0(0:ingress/1:egress) lost type is 192 in 8 slot.
#Jun 13 19:19:00 2008 IPCTL-ZJM-SSP3000-A FLOWSEC/5/TRAP:1.3.6.1.4.1.2011.25.125.9.2.1 index: 0 There are 017930 packets lost at 
 
Handling Process
1. Because the packet loss alarms are about the slot of the GE interface and the POS interface, check the port status. There is no packet loss caused by the Down status of the ports or the POS link.
2. The alarms are confirmed to be about the loss of protocol packets, which do not affect the services and can be screened. For V500R003, run the undo flowsec trap enable command to close the trap message, which does not prevent the system from giving other alarms.
3. Way to screen the alarms:
After the snmp-agent trap enable command enables the trap message in the V500R003 environment, run the undo flowsec trap enable command to close the packet loss alarms of the SSP, which does not prevent the system from giving other trap message. In addition, the configuration enabled by the undo flowsec trap enable command can be saved.
Note: After the undo flowsec trap enable command is run, running the snmp-agent trap enable command again to enable the trap message can re-open the trap message about the packet loss because snmp-agent trap enable is a general command and undo flowsec trap enable is a command related to the packet classification feature of the SSP. 
 
Root Cause
The alarms are about the loss of protocol packets and the packet loss caused by the traffic flowing through the ports that are down.
The SSP cares nothing about protocol packets. Therefore, all such packets received are discarded directly.
Such a type of packet loss does not affect the SSP services.
ets lost at 0(0:ingress/1:egress) lost type is 192 in 4 slot. You can determine the cause for packet loss according to the value of 192 indicating lost type. 
 
Suggestions
SSP3000 is the traffic splitting platform of the NE5000E. 

END