Presentation is loading. Please wait.

Presentation is loading. Please wait.

Packet Drop in HP Switches Guoming. Cause: packet based hashing in F10 LAG + HP switch buffer Assumption: link utilization 50% In the hashing, several.

Similar presentations


Presentation on theme: "Packet Drop in HP Switches Guoming. Cause: packet based hashing in F10 LAG + HP switch buffer Assumption: link utilization 50% In the hashing, several."— Presentation transcript:

1 Packet Drop in HP Switches Guoming

2 Cause: packet based hashing in F10 LAG + HP switch buffer Assumption: link utilization 50% In the hashing, several events with varied IP_ID could use the same output link, but from long term’s view, the load is still balanced very well among all LAG members Example: 4 1 F10 Ports 231 HP Switch 2 3 4 1 423 Congestion 1 Event, 1: destination 1 Another round after have sent to all farm nodes

3 What makes thing worse? HP switch available buffer: 350 ~ 500 KB Available buffer depends on the frame size Big event size e.g. the case in slide 2: two events contest the same output port in HP, packets get dropped if the event size is bigger the buffer

4 Simulation Studies with simulation Assumptions / simplifications 1) All frames have the same size 2) Full farm size: 5-port LAG X 100, 30 nodes/rack 3) To speed up the simulation: 12 pkts/event, 1.2 KB/frame

5 Result: Max. Queue Length vs MEP factor 12 pkts/event Link utilization: 80% No clear correlation between Queue length and MEP factor Mep factor 123456789101112131415 F10Q Max (pkt)‏ 140 182152176197164155191197215167149161224 HPQ Max (pkt)‏ 211921122122181219 2124221322

6 Result: Max. Queue Length vs link number per LAG Link utilization: 80% Link number/LAG 5678 F10Q Max 15513116833 HPQ Max 1222216

7 Result: Max. Queue Length vs link utilization 5 links/LAG X100 Link Utilization (%)‏60 70 809095 F10Q Max99 131 155185265 HPQ Max9 12 2231

8 Possible solutions Enable flowcontrol Others if flowcontrol does not help – Small MEP factor – Change IP_IDENT (see the result in next slide)‏ 1) half with IP_IDENT, the other half with IP_IDENT+1 2) 1/3 IP_IDENT, 1/3 IP_IDENT+1, 1/3 IP_IDENT+2 3) some other schemes... – Change back to the original scheme: no LAG, small VLAN – Feature request for F10: round-robin hashing – Upgrade HP switches

9 Simulation Result: changing IP_IDENT (1)‏ 1/2 + 1/2 1/3 + 1/3+ 1/3 Link Utilization (%)‏ 60 70 809095 F10Q Max 31 41 4870104 HPQ Max 8 8 81213 Link Utilization (%)‏ 60 70 809095 F10Q Max 49 69 101136160 HPQ Max 6 12 13 16


Download ppt "Packet Drop in HP Switches Guoming. Cause: packet based hashing in F10 LAG + HP switch buffer Assumption: link utilization 50% In the hashing, several."

Similar presentations


Ads by Google