Netlog Usage Considerations
Article ID: 41079456
Examples of reasons to use the netlog
- Customer is reporting delays and/or disconnects during client-host session activity (conducted over wifi); problems are more apt to occur when devices are roaming.
- Customer is reporting inconsistent IP delivery when DHCP is configured.
- Customer is reporting inconsistent session continuance after roams and/or while stationary.
- Customer is reporting the possibility of roam excess and/or wireless disconnects.
Netlog is designed to capture Ethernet traffic (TCP/IP), EAP & EAPOL protocol frames from the device perspective. If you wish to capture breakdowns during the client-host session exchange, it is most useful.
Netlog is also helpful for determining authentication performance consistency during the security challenge of both client & AP/authenticator, when either form of WPA/WPA2 is used (both Personal & Enterprise).
Netlog can also aid in determining if proper Fast Roam functionality is performed as well as all TCP/IP functions: (IP management, ARP, DNS, etc) as they may directly affect session flow & session continuance.
Note If wireless connectivity concerns are also reported, since netlog cannot capture any lower layer/RF traffic, its always best to accompany the concurrent Fusion log with all netlog trace data collected (make sure the system time/date is set on device before test). Having the Fusion log will provide a low-level assessment of wireless functionality as it may correlate to the activity seen in netlog. In severe cases where the Fusion log may lack granularity, then a wireless sniffer trace/capture may be necessary.
Please review the solution "Installing Netlog on Mobile Units Running Microsoft OS" for information on how to install Netlog on a Mobile Unit. Read More>>