Advertisement
Guest User

Untitled

a guest
Apr 2nd, 2020
283
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.66 KB | None | 0 0
  1.  
  2. Skip to content
  3. Using Gmail with screen readers
  4. 1 of 26
  5. Networking issue
  6. Inbox
  7. x
  8. phil pt <ptaylor2446@gmail.com>
  9.  
  10. Wed, Apr 1, 9:40 AM (23 hours ago)
  11.  
  12. to qm
  13. Now for the second time your company was in the wrong for not contacting your per customer level3.net about the network issue I was having connecting to the server located in st.louis, mo. This shows that your unable to do you job the correct way.
  14.  
  15. Cox.Net my ISP has informed me that they saw a issue t level3.net so you wrong again. When are you going to start doing your job the correct way.
  16.  
  17. |------------------------------------------------------------------------------------------|
  18. | WinMTR statistics |
  19. | Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
  20. |------------------------------------------------|------|------|------|------|------|------|
  21. | RT-AC1900P-9BC0 - 17 | 1974 | 1652 | 0 | 1 | 114 | 1 |
  22. | 10.7.0.1 - 1 | 3149 | 3128 | 6 | 10 | 361 | 9 |
  23. | 100.118.110.156 - 1 | 3111 | 3080 | 7 | 11 | 159 | 8 |
  24. | 100.121.20.8 - 1 | 3157 | 3138 | 5 | 12 | 392 | 10 |
  25. | ashbbprj01-ae2.rd.as.cox.net - 1 | 3150 | 3129 | 7 | 13 | 125 | 9 |
  26. | lag-196.bear1.Washington111.Level3.net - 100 | 654 | 3 | 0 | 10 | 13 | 10 |
  27. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  28. | dcx4-brdr-01.inet.qwest.net - 1 | 3134 | 3109 | 8 | 13 | 222 | 9 |
  29. | los-edge-08.inet.qwest.net - 1 | 3134 | 3109 | 75 | 81 | 263 | 80 |
  30. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  31. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  32. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  33. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  34. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  35. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  36. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  37. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  38. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  39. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  40. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  41. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  42. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  43. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  44. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  45. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  46. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  47. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  48. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  49. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  50. | No response from host - 100 | 652 | 0 | 0 | 0 | 0 | 0 |
  51. |________________________________________________|______|______|______|______|______|______|
  52. WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
  53.  
  54.  
  55. |------------------------------------------------------------------------------------------|
  56. | WinMTR statistics |
  57. | Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
  58. |------------------------------------------------|------|------|------|------|------|------|
  59. | RT-AC1900P-9BC0 - 11 | 3264 | 2932 | 0 | 1 | 104 | 0 |
  60. | 10.7.0.1 - 1 | 4462 | 4436 | 5 | 9 | 127 | 13 |
  61. | 100.118.110.158 - 2 | 4376 | 4328 | 7 | 11 | 381 | 10 |
  62. | 100.121.20.10 - 1 | 4453 | 4425 | 6 | 12 | 222 | 7 |
  63. | ashbbprj01-ae2.rd.as.cox.net - 1 | 4456 | 4429 | 7 | 13 | 447 | 11 |
  64. | lag-196.bear1.Washington111.Level3.net - 100 | 919 | 1 | 0 | 8 | 8 | 8 |
  65. | ae-2-7.bear2.StLouis1.Level3.net - 77 | 1133 | 268 | 30 | 33 | 49 | 33 |
  66. | ae5.cr-rigel.stl1.core.heg.com - 1 | 4470 | 4446 | 29 | 33 | 422 | 38 |
  67. | 207.38.95.10 - 1 | 4430 | 4397 | 29 | 33 | 300 | 30 |
  68. | 207.38.80.34 - 1 | 4453 | 4425 | 29 | 36 | 252 | 33 |
  69. |static-ip-209-239-125-3.inaddr.ip-pool.com - 1 | 4446 | 4416 | 30 | 35 | 263 | 33 |
  70. |static-ip-69-64-49-219.inaddr.ip-pool.com - 1 | 4429 | 4394 | 29 | 32 | 235 | 31 |
  71. |________________________________________________|______|______|______|______|______|______|
  72. WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
  73.  
  74. SERVER4YOU - Qualitätsmanagement <qualitaetsmanagement@server4you.de>
  75.  
  76. 4:58 AM (3 hours ago)
  77.  
  78. to me, qm
  79.  
  80. Dear Mr. Taylor,
  81.  
  82. My name is Kai Bluhm, I am responsible for complaint and quality management in the company. I am sure that if we work together and you provide us with the information we need, we will be able to find a solution or a way to solve the problem.
  83.  
  84. As our colleagues have correctly written, the provided traceroutes are not usable in our view. A traceroute or ping is intentionally interrupted within our network. It is a security mechanism to conceal our structure in detail. A common means in our industry.
  85.  
  86. This morning I asked my colleagues in the network department whether they had noticed any anomalies in and around the network of the St. Louis data center in the past few days. This was denied with the request to provide detailed information so that we can investigate.
  87.  
  88. We require, and this is not negotiable, an MTR from the target and source for at least 15 minutes at the time of the disruption. A few seconds may tell you that nothing works there, but it does not help us to identify the cause.
  89.  
  90. Therefore, there is no other option for you than to comply with our request and provide us with the information we need. If with the information, we have now received, you still do not send the two required MTR log files, we cannot help you.
  91.  
  92. Please send me the necessary information directly in response to this message without changing the subject. And please do yourself and us the favor of not opening new processes for the time being. This would only complicate my work and thus a possible solution finding at your expense.
  93.  
  94. If you have any difficulties in understanding my explanation, please let me know as well. As already mentioned at the beginning I am sure that we will find a solution together. But for this, we have to work together.
  95.  
  96. Thank you for your time and thank you in advance for the information required.
  97.  
  98. Best regards,
  99. Kai Bluhm
  100. Complaint Management
  101. --
  102.  
  103. New Acronis Backup
  104. Acronis Backup is the perfect backup solution for your server infrastructure providing backup and recovery of physical and virtual machines, files, and databases to our storage servers.
  105. You no longer need to worry about data loss and can restore your system at any time.
  106. You can order Acronis Backup through your customer panel under Hardware > Acronis Backup.
  107. --
  108. HEG US Inc.
  109. 210 North Tucker Blvd., Suite 910
  110. Saint Louis, MO 63101
  111. United States of America
  112. phil pt <ptaylor2446@gmail.com>
  113.  
  114. 6:51 AM (2 hours ago)
  115.  
  116. to SERVER4YOU
  117. The MTR report on the last issue is included the closed tickets. I do not agree with the your statement that you agree with your colleagues because twice Cox Communications Support, Networking and the Cox Communication Operations center forwarded the tickets up to their peers because there was in fact a issue in the peer customers.
  118.  
  119. This was already proven please refer to the closed tickets that include the email from Cox Communication Center.
  120.  
  121. The trace routes where also included in the tickets to show that the high ms on the backbones where way above normal cox communication also agree with me on this issue. Sorry, I do not trust your techs and I have more trust with the information that Cox Communications is providing to me.
  122.  
  123. For the network issue this has already happened twice in the past 5 days. This is not being constructive or being productive. I am only one person in my company and the amount of time I am spending on this issue is not justified.
  124.  
  125. Please refer back to the open and closed tickets. If you do not have access to them then please let me know and I will provide you with the information.
  126.  
  127. Thanks
  128. Phil Taylor
  129. phil pt <ptaylor2446@gmail.com>
  130.  
  131. 7:01 AM (1 hour ago)
  132.  
  133. to SERVER4YOU
  134. I forgot to say that in order to resolve network issue as a professional network administrator for the past 30 years using all the visions of windows, Linux, Unix and Freebsd you have to use both the MTR and traceroutes in order to determine the location of the issue. The traceroutes where way above the normal ms on the traceroutes on several hops on both issues on the last ticket and the one I submitted several days before on a separate network issue.
  135.  
  136. This is the proper way and is within the normal procedures as Cox Comminication Network guidelines that they follow at the knock ISP center to fix network issues. Trust me I have being doing this for a very long time, and I probably have more experience then most of your employees at the St.Louis Data Center.
  137. SERVER4YOU - Qualitätsmanagement
  138.  
  139. 7:07 AM (1 hour ago)
  140.  
  141. to me
  142.  
  143. Dear Mr. Taylor,
  144.  
  145. As already explained several times: traceroutes are absolutely useless. You have my offer. Just send me the information and I will gladly forward it to the colleagues in the network team.
  146.  
  147. If you do not want this, it is your decision. I have explained what I need and why I need it. At this point in time and without the requested information I cannot do more for you.
  148.  
  149. I thank you for your understanding and hope you will reconsider your decision. As already mentioned, only together we will get a solution. And what you have formulated as an answer is unfortunately very far from the willingness to cooperate.
  150. phil pt <ptaylor2446@gmail.com>
  151.  
  152. 8:53 AM (4 minutes ago)
  153.  
  154. to SERVER4YOU
  155. What information do you need please?
  156. phil pt <ptaylor2446@gmail.com>
  157.  
  158. 8:56 AM (0 minutes ago)
  159.  
  160. to SERVER4YOU
  161. MTR reports for the past 18 hours. your wrong the traceroutes are is tool to help determine network issues.
  162.  
  163. |------------------------------------------------------------------------------------------|
  164. | WinMTR statistics |
  165. | Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
  166. |------------------------------------------------|------|------|------|------|------|------|
  167. | RT-AC1900P-9BC0 - 17 | 21857 | 18183 | 0 | 1 | 128 | 1 |
  168. | 10.7.0.1 - 1 | 35539 | 35341 | 4 | 9 | 173 | 8 |
  169. | 100.118.110.158 - 1 | 35391 | 35154 | 6 | 10 | 140 | 9 |
  170. | 100.121.20.10 - 1 | 35538 | 35339 | 5 | 11 | 403 | 112 |
  171. | ashbbprj01-ae2.rd.as.cox.net - 1 | 35445 | 35222 | 6 | 12 | 352 | 9 |
  172. | lag-196.bear1.Washington111.Level3.net - 99 | 7402 | 107 | 0 | 23 | 558 | 9 |
  173. | ae-2-7.bear2.StLouis1.Level3.net - 52 | 11948 | 5789 | 29 | 33 | 570 | 32 |
  174. | ae5.cr-rigel.stl1.core.heg.com - 1 | 35485 | 35273 | 27 | 33 | 571 | 33 |
  175. | 207.38.95.10 - 1 | 35508 | 35302 | 27 | 33 | 269 | 33 |
  176. | 207.38.80.34 - 1 | 35565 | 35375 | 27 | 36 | 273 | 35 |
  177. |static-ip-209-239-125-3.inaddr.ip-pool.com - 1 | 35244 | 34970 | 29 | 35 | 375 | 33 |
  178. |static-ip-69-64-49-219.inaddr.ip-pool.com - 1 | 35450 | 35229 | 27 | 32 | 270 | 32 |
  179. |________________________________________________|______|______|______|______|______|______|
  180. WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement