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

S9300 inter-board aggregation interface limit rate is differ from actual test result

Publication Date:  2012-11-21 Views:  3 Downloads:  0
Issue Description
Version:V100R002C00SPC200

Topology:ME60---------S9300(Eth-Trunk24)=======L2---------PC (192.168.67.10)

failure:S9300 limit to 2M for Eth-Trunk 24 outbound IP address,test on PC side, the load result reached 3~4M,test result is not correct.

data configuration:
interface Vlanif4020
  ip binding vpn-instance tldkh
  ip address 192.168.67.1 255.255.255.0
  dhcp select global
#
acl number 3030
  rule 5 permit ip destination 192.168.67.0 0.0.0.255
  rule 10 permit ip destination 192.168.58.64 0.0.0.63
#
traffic classifier clh-down operator or precedence 30
  if-match acl 3030
traffic behavior clh-down
  car cir 2048 pir 2048 cbs 385024 pbs 641024 mode color-blind green pass yellow pass red discard
traffic policy clh-down
  classifier clh-down behavior clh-down
#
interface Eth-Trunk24
  port link-type trunk
  port trunk allow-pass vlan 3500 to 3501 3542 4020 to 4021
  traffic-policy clh-down outbound
#
interface GigabitEthernet2/0/3
  Eth-Trunk 24
#
interface GigabitEthernet1/0/3
  Eth-Trunk 24

Alarm Information
NULL
Handling Process
1、The following acl configuration,associate with flow behavior,it appointed to each rule limit 2M.

acl number 3030
  rule 5 permit ip destination 192.168.67.0 0.0.0.255
  rule 10 permit ip destination 192.168.58.64 0.0.0.63

2、The failure is related with  aggregation interface handling 
Firstly,define traffic policy 2M car, applied eth-trunk 24 is inter-board 2 ports, each board is 2M;

Secondly,test PC as destination IP fixed,if source ip is fixwd,then traffic hash should be fixed on one port, so the max value is 2M;

3、Current network test with Thunder software,  segment source may exist in muti server, so soure IP is not only one, after taffic aggregation interface hash, 93 pass down from 2 ports, the test rate may more than 2M, but it will not more than 4M.

It suggested that modify the source Ip as some fixed server, the test result will accord the theoretics conjecture.

Root Cause
1、Configuration is correct, PC IP address can match acl,exclude the setting problem.

2、It doubt that limit way is related to aggregation interface handling logic.
Suggestions
Contrapose to aggregation interface limit rate, aggregation interface board is shared, that is all the ports under aggregation interface use the same car, inter-board is exclusive, that all ports of each board in aggregation interface use the same car.

END