w ry o go roug eac ype o rao ecnoogy antry to point out the important factor for that specifictechnology. (Try to memorize all the steps listed abovesicne I will talk about the steps for each of the followingsections).
What kind of tools we need for troubleshoot ?
i) LAN Cable type (Sometimes you have to use 'direct cable'and sometimes you have to use 'cross over' cable).ii) Category of LAN cable. (Is it Cat 5 cable or Cat 6 cable ?)iii) Ethernet Port Capability (Is it only for 10/100 M, orGigabit ethernet ?)iv) Firewall setting on your PC (I will go back to this later ina separate section).iv) YOUR SKILLs to use and analyze the logging toolv) YOUR PATIENCE to step through the log for each andevery transmission and receptionSince the throughput process get involved in the fullprotocol stack and one/two PCs, and in addition IP tools,you would need to have tools to monitor each and everysteps along the end-to-end data path. The logging toolshould be able to show not only scheduling and event log,but also all the payload (contents of the data). Withoutthese tools, you would end up saying "I have tested thisdevice with many different test equipment and didn't seeany problem before. This is the only equipment that I seethis problem.. so the problem is on the equipment side." or"I have tested many different UE with this equipment, but Ididn't see this kind of problem before. So this is UE sideproblem". Both may be right or wrong at the same time.Our job as an engineer is to find the root cause of theproblem and fix it, not blaming the other party. (But to behonest, I have to admit I often blame the other partywithout even realizing it. Is this a kind of bad nature of engineers ? or my personal problem ?)Let's try to have proper tools and skills to fight against theproblem, not fight against your counter part engineers. Myrecommendation about the tool is as follows :i) Ethernet, IP logging tool (e.g, Wireshark)ii) UE side logging tooliii) Network side logging tool