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

IPush function carries on advertisement push, successful, but can’t see the pushed advertisement on the browser

Publication Date:  2012-11-14 Views:  27 Downloads:  0
Issue Description
IPush function carries on advertisement push, through the Debug command the pushed policy has been dispensed successfully, advertisement push successful, but can’t see the pushed advertisement on the browser. 
Alarm Information
None.
Handling Process
1, increase the Web page size of the target server;
2, configure the link between the client and the target server to10M half duplex;
3, add more network elements between the client and the target server.
Root Cause
 On the client open capture tools, push again, phenomenon recur, check the captured message, there exists an obsolete Redirect message;
Check the Redirect message’s MAC address, through checking can confirm the message is sent from the interference of the SIG port;
Check the Redirect message’s TCP ACK values, and in a response TCP message before it, found the same TCP ACK value;
According to the principle of the iPush characteristics, the client sent a request to the target server, after detected to the request, SIG will send a Redirect message to client in the name of the target server, redirect to SIG’s AD server.
If the target server responded too fast, the response message prior to Redirect message to reach to client, due to has the consistent TCP ACK value, the later reached message will directly be cancelled by system, leading to can’t see the advertisement when pushing.
Suggestions
According to the iPush characteristic specifications, the reaction time of the characteristics is 3 ms, namely after SIG detected to request message, need 3ms processing time, just can send the Redirect message out.
The situation in general appears in testing or experiment environment, in the complex live network environment rarely appears this problem, but does not exclude it will not appear the circumstance in enterprise network deployment.

END