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>


To have a better experience, please upgrade your IE browser.


Corporate HTTP Browsing Issue Because of Different Realization Between NE40E and SE400

Publication Date:  2015-01-13 Views:  103 Downloads:  0
Issue Description
Handling Process
There are 3 subnets, which are GGC, Akamai belongs class Proxy, unfortunately, there are also belongs to class tata6 as well which will be redirect to F5. Since we put classifier tata6 before Proxy, so traffic with destination to GGC/Akamai, which supposed to be bypassed, will be redirect to F5, this is what F5 team find.
Root Cause
This issue was due to the different realization of forwad policy/traffic policy between E/// SE400 and Huawei NE40E. SE400 match traffic with with rules sequence one by one, while NE40E match traffic by classifiers.
We define a new classifier which included GGC/Akamai subnets with bypass behavior, and put this classifier at the first classifier. Incoming traffic with destination IP address to GGC/Akamai will match this classifier and go internet directly.