[AusNOG] Vocus Melbourne Outage

Mark ZZZ Smith markzzzsmith at yahoo.com.au
Thu Jan 8 08:42:43 EST 2015



So this email reads to me like your first action after discovering an apparent fault *inside* the TPG network was to bother 2000+ AusNOG subscribers with a traceroute output that doesn't even demonstrate that Vocus are involved.

If this is the case, then you should be doing a lot more troubleshooting if you send out an "is it up" email to the mailing list. 

TPG are your upstream provider, so you should first be lodging a fault with them and letting them sort out what the fault with their network is (whether it is their own gear or somebody else's service).

If you did contact TPG before sending this email, you still really shouldn't be bothering this list as you just need to wait until TPG get it fixed (and perhaps spend time investigating redundant connectivity if they're taking too long.)

People need to remember that this list isn't the first point of contact for solving trivial faults (and in the networks that are operated by many people on this list, a broken link is a trivial fault).

I'll assume you haven't read the new charter; it includes both good and (very) bad examples of fault emails, and your's is pretty close to the bad one:


GOOD:


Hi,

We are seeing problems with packets to ISP X disappearing into the
ether at A.B.C.D, but only when traversing ISP Y and ISP Z.
This only happens on the waxing moon from a random set of IP addresses.

Has anyone else seen this problem? How did you resolve it?
We have not been able to get in touch with either ISP Y or ISP Z
through the normal channels and I'm not sure they are aware of it.

S. Marty,
AweSome Nets Limited



VERY BAD:

Can someone from ISP X please contact me off list. You are broken.

A. Dolt,
Dolt Network Services Pty Ltd




>________________________________
> From: Daniel <daniel at dwatson.me>
>To: ausnog at lists.ausnog.net 
>Sent: Wednesday, 7 January 2015, 22:50
>Subject: [AusNOG] Vocus Melbourne Outage
> 
>
>
>Gday Noggers
> 
>Anybody else having issues with Vocus in Melbourne?
> 
>C:\Users\danie_000>tracert 103.18.204.2
> 
>Tracing route to 2-204-18-103.static.glovine.com.au [103.18.204.2]
>over a maximum of 30 hops:
> 
>  1    <1 ms    <1 ms    <1 ms  192-168-1-1.tpgi.com.au [192.168.1.1]
>  2    30 ms    30 ms    30 ms  10.20.20.196
>  3    32 ms    37 ms    30 ms  nme-sot-dry-agr1-Te1-6.tpgi.com.au [202.7.173.14
>1]
>  4    32 ms    31 ms    62 ms  nme-sot-dry-crt2-Te0-1-0-5.tpgi.com.au [203.29.1
>40.189]
>  5    42 ms    42 ms    43 ms  203-219-106-237.tpgi.com.au [203.219.106.237]
>  6    42 ms    43 ms    42 ms  syd-gls-har-int1-be-20.tpgi.com.au [203.29.129.1
>95]
>  7     *        *        *     Request timed out.
>  8     *        *        *     Request timed out.
>  9     *        *        *     Request timed out.
>10     *        *        *     Request timed out.
>11     *        *        *     Request timed out.
>12     *        *        *     Request timed out.
>13     *        *        *     Request timed out.
>14     *        *        *     Request timed out.
>15     *        *        *     Request timed out.
>16     *        *        *     Request timed out.
>17     *        *        *     Request timed out.
>18     *        *        *     Request timed out.
>19     *        *        *     Request timed out.
>20     *        *        *     Request timed out.
>21     *        *        *     Request timed out.
>22     *        *        *     Request timed out.
>23     *        *        *     Request timed out.
>24     *        *        *     Request timed out.
>25     *        *        *     Request timed out.
> 
> 
>D.
>_______________________________________________
>AusNOG mailing list
>AusNOG at lists.ausnog.net
>http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
>


More information about the AusNOG mailing list