API tools faq
paste
Advertisement
mightymouse2045

AICCU output

mightymouse2045
Jun 5th, 2012
159
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.13 KB | None | 0 0
raw download clone embed print report
  1. /usr/sbin/aiccu autotest
  2. Tunnel Information for T95806:
  3. POP Id : uschi03
  4. IPv6 Local : 2604:8800:100:176::2/64
  5. IPv6 Remote : 2604:8800:100:176::1/64
  6. Tunnel Type : 6in4-heartbeat
  7. Adminstate : enabled
  8. Userstate : enabled
  9. RTNETLINK answers: File exists
  10. #######
  11. ####### AICCU Quick Connectivity Test
  12. #######
  13.  
  14. ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (10.5.0.3)
  15. ### This should return so called 'echo replies'
  16. ### If it doesn't then check your firewall settings
  17. ### Your local endpoint should always be pingable
  18. ### It could also indicate problems with your IPv4 stack
  19.  
  20. PING 10.5.0.3 (10.5.0.3) 56(84) bytes of data.
  21. 64 bytes from 10.5.0.3: icmp_req=1 ttl=64 time=0.019 ms
  22. 64 bytes from 10.5.0.3: icmp_req=2 ttl=64 time=0.015 ms
  23. 64 bytes from 10.5.0.3: icmp_req=3 ttl=64 time=0.025 ms
  24.  
  25. --- 10.5.0.3 ping statistics ---
  26. 3 packets transmitted, 3 received, 0% packet loss, time 1998ms
  27. rtt min/avg/max/mdev = 0.015/0.019/0.025/0.006 ms
  28.  
  29. ######
  30.  
  31. ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (38.229.76.3)
  32. ### These pings should reach the PoP and come back to you
  33. ### In case there are problems along the route between your
  34. ### host and the PoP this could not return replies
  35. ### Check your firewall settings if problems occur
  36.  
  37. PING 38.229.76.3 (38.229.76.3) 56(84) bytes of data.
  38. 64 bytes from 38.229.76.3: icmp_req=1 ttl=49 time=237 ms
  39. 64 bytes from 38.229.76.3: icmp_req=2 ttl=49 time=236 ms
  40. 64 bytes from 38.229.76.3: icmp_req=3 ttl=49 time=236 ms
  41.  
  42. --- 38.229.76.3 ping statistics ---
  43. 3 packets transmitted, 3 received, 0% packet loss, time 2001ms
  44. rtt min/avg/max/mdev = 236.260/236.931/237.869/0.683 ms
  45.  
  46. ######
  47.  
  48. ####### [3/8] Traceroute to the PoP (38.229.76.3) over IPv4
  49. ### This traceroute should reach the PoP
  50. ### In case this traceroute fails then you have no connectivity
  51. ### to the PoP and this is most probably the problem
  52.  
  53. sh: 1: traceroute: not found
  54.  
  55. ######
  56.  
  57. ###### [4/8] Checking if we can ping IPv6 localhost (::1)
  58. ### This confirms if your IPv6 is working
  59. ### If ::1 doesn't reply then something is wrong with your IPv6 stack
  60.  
  61. PING ::1(::1) 56 data bytes
  62. 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.023 ms
  63. 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.019 ms
  64. 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.023 ms
  65.  
  66. --- ::1 ping statistics ---
  67. 3 packets transmitted, 3 received, 0% packet loss, time 1998ms
  68. rtt min/avg/max/mdev = 0.019/0.021/0.023/0.005 ms
  69.  
  70. ######
  71.  
  72. ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2604:8800:100:176::2)
  73. ### This confirms that your tunnel is configured
  74. ### If it doesn't reply then check your interface and routing tables
  75.  
  76. PING 2604:8800:100:176::2(2604:8800:100:176::2) 56 data bytes
  77. 64 bytes from 2604:8800:100:176::2: icmp_seq=1 ttl=64 time=0.015 ms
  78. 64 bytes from 2604:8800:100:176::2: icmp_seq=2 ttl=64 time=0.025 ms
  79. 64 bytes from 2604:8800:100:176::2: icmp_seq=3 ttl=64 time=0.048 ms
  80.  
  81. --- 2604:8800:100:176::2 ping statistics ---
  82. 3 packets transmitted, 3 received, 0% packet loss, time 1998ms
  83. rtt min/avg/max/mdev = 0.015/0.029/0.048/0.014 ms
  84.  
  85. ######
  86.  
  87. ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2604:8800:100:176::1)
  88. ### This confirms the reachability of the other side of the tunnel
  89. ### If it doesn't reply then check your interface and routing tables
  90. ### Don't forget to check your firewall of course
  91. ### If the previous test was successful then this could be both
  92. ### a firewalling and a routing/interface problem
  93.  
  94. PING 2604:8800:100:176::1(2604:8800:100:176::1) 56 data bytes
  95.  
  96. --- 2604:8800:100:176::1 ping statistics ---
  97. 3 packets transmitted, 0 received, 100% packet loss, time 2016ms
  98.  
  99.  
  100. ######
  101.  
  102. ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
  103. ### This confirms that you can reach the central machine of SixXS
  104. ### If that one is reachable you should be able to reach most IPv6 destinations
  105. ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
  106. ### If your browser supports IPv6 and uses it of course.
  107.  
  108. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2604:8800:100:8176::2, 30 hops max, 24 byte packets
  109. 1 877w (2604:8800:100:8176::1) 1.966 ms 1.423 ms 1.056 ms
  110. 2 gw-375.chi-03.us.sixxs.net (2604:8800:100:176::1) 237.558 ms 238.316 ms 238.245 ms
  111. 3 2620:0:6b0:a::53:1 (2620:0:6b0:a::53:1) 247.293 ms 238.202 ms 237.945 ms
  112. 4 2620:0:6b0:a::1 (2620:0:6b0:a::1) 238.461 ms 237.476 ms 248.163 ms
  113. 5 ge-4-35.car2.Chicago2.Level3.net (2001:1900:2100::171) 324.697 ms 295.005 ms *
  114. 6 vl-52.edge1.Chicago2.Level3.net (2001:1900:37:2::3) 293.045 ms 292.516 ms 292.215 ms
  115. 7 vl-4067.car1.Chicago1.Level3.net (2001:1900:4:1::1d) 298.095 ms 293.746 ms 294.209 ms
  116. 8 vl-4061.car2.NewYork2.Level3.net (2001:1900:4:1::22) 303.589 ms 296.339 ms 295.668 ms
  117. 9 vl-4060.car2.NewYork1.Level3.net (2001:1900:4:1::fd) 293.945 ms 294.411 ms 293.686 ms
  118. 10 2001:1900:19:5::6 (2001:1900:19:5::6) 294.098 ms 292.97 ms 293.822 ms
  119. 11 EASYNET-GRO.NewYork1.Level3.net (2001:1900:4:2::2b2) 270.739 ms 273.527 ms 270.335 ms
  120. 12 2001:6f8:1:0:87:86:77:110 (2001:6f8:1:0:87:86:77:110) 354.447 ms 347.24 ms 349.529 ms
  121. 13 2001:6f8:1:0:87:86:77:121 (2001:6f8:1:0:87:86:77:121) 341.691 ms 333.728 ms 331.982 ms
  122. 14 2001:6f8:1:0:87:86:77:31 (2001:6f8:1:0:87:86:77:31) 469.87 ms 340.733 ms 339.648 ms
  123. 15 2001:6f8:1:0:87:86:77:46 (2001:6f8:1:0:87:86:77:46) 342.021 ms 339.457 ms 339.233 ms
  124. 16 2001:6f8:1:0:87:82:50:232 (2001:6f8:1:0:87:82:50:232) 350.807 ms 341.725 ms 341.033 ms
  125. 17 2001:838:5:9::2 (2001:838:5:9::2) 344.164 ms 345.101 ms 345.187 ms
  126. 18 2001:838:5:8::2 (2001:838:5:8::2) 345.122 ms 344.584 ms 344.891 ms
  127. 19 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 345.676 ms 349.285 ms 353.456 ms
  128.  
  129. ######
  130.  
  131. ###### [8/8] Traceroute6 to (www.kame.net)
  132. ### This confirms that you can reach a Japanese IPv6 destination
  133. ### If that one is reachable you should be able to reach most IPv6 destinations
  134. ### You should also check http://www.kame.net which should display
  135. ### a animated kame (turtle), of course only when your browser supports and uses IPv6
  136.  
  137. traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2604:8800:100:8176::2, 30 hops max, 24 byte packets
  138. 1 877w (2604:8800:100:8176::1) 0.979 ms 0.962 ms 0.963 ms
  139. 2 gw-375.chi-03.us.sixxs.net (2604:8800:100:176::1) 236.518 ms 235.475 ms 236.055 ms
  140. 3 2620:0:6b0:a::53:1 (2620:0:6b0:a::53:1) 236.762 ms 236.229 ms 236.005 ms
  141. 4 2620:0:6b0:a::1 (2620:0:6b0:a::1) 240.164 ms 236.082 ms 236.014 ms
  142. 5 * * ge-4-35.car2.Chicago2.Level3.net (2001:1900:2100::171) 298.609 ms
  143. 6 vl-52.edge4.Chicago3.Level3.net (2001:1900:37:2::6) 296.403 ms 292.563 ms 290.865 ms
  144. 7 ntt-level3-10G.Chicago3.Level3.net (2001:1900:4:3::72) 294.859 ms 309.889 ms 295.649 ms
  145. 8 ae-7.r20.chcgil09.us.bb.gin.ntt.net (2001:418:0:2000::4d) 274.2 ms 279.547 ms 252.157 ms
  146. 9 ae-5.r20.sttlwa01.us.bb.gin.ntt.net (2001:418:0:2000::145) 334.546 ms 334.147 ms 437.01 ms
  147. 10 as-3.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::22) 399.735 ms 419.341 ms 399.991 ms
  148. 11 ae-1.r24.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::11a) 400.773 ms 400.319 ms 400.139 ms
  149. 12 po-1.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::10e) 404.082 ms 404.619 ms 405.117 ms
  150. 13 ge-8-2.a15.tokyjp01.jp.ce.gin.ntt.net (2001:218:2000:5000::82) 426.243 ms 415.157 ms 400.58 ms
  151. 14 ve44.foundry6.otemachi.wide.ad.jp (2001:200:0:10::141) 400.941 ms 398.984 ms 398.086 ms
  152. 15 ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 422.543 ms 400.836 ms 399.797 ms
  153. 16 cloud-net1.wide.ad.jp (2001:200:0:1c0a:218:8bff:fe43:d1d0) 420.054 ms 407.997 ms 400.648 ms
  154. 17 2001:200:dff:fff1:216:3eff:feb1:44d7 (2001:200:dff:fff1:216:3eff:feb1:44d7) 409.501 ms 430.252 ms 408.806 ms
  155.  
  156. ######
  157.  
  158. ###### ACCU Quick Connectivity Test (done)
  159.  
  160. ### Either the above all works and gives no problems
  161. ### or it shows you where what goes wrong
  162. ### Check the SixXS FAQ (http://www.sixxs.net/faq/
  163. ### for more information and possible solutions or hints
  164. ### Don't forget to check the Forums (http://www.sixxs.net/forum/)
  165. ### for a helping hand.
  166. ### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!