[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ATT NOC

Subject: ATT NOC
From: ghenry at suretec.co.uk (Gavin Henry)
Date: Tue, 10 Oct 2017 18:00:46 +0100
In-reply-to: <CAMgUhppgYz8d0mX7sy=aOxEygbshBf+SLE1g6FRT9DLaRo06rw@mail.gmail.com>
References: <CAPcb_GLZPoi2rm_hvzEKSkvjpRL2x92suCGuKntbMt7_QpPkAw@mail.gmail.com> <CAMgUhppGrr4fDSzEd-hAd50HDcMnxUZr-cwMpzOgKuUqUXVGLQ@mail.gmail.com> <CAPcb_GJfd0uvgjOD2QdsY9kgphs-34k0HG=UawTD=W1rdpmaGw@mail.gmail.com> <CAMgUhppgYz8d0mX7sy=aOxEygbshBf+SLE1g6FRT9DLaRo06rw@mail.gmail.com>

On 10 October 2017 at 17:47, Nimrod Levy <nimrodl at gmail.com> wrote:
> We're not accepting the route from our peers due to the AS-SET in the path:
>   174 199659 {65002}, (aggregated by 199659 10.10.10.3), (received-only)
>   2914 199659 {65002}, (aggregated by 199659 10.10.10.1), (received-only)

Thanks Nimrod,

I'll speak to our transit providers again to see where 65002 is coming from.

Gavin.

Follow-Ups:
- ATT NOC
  - From: ghenry at suretec.co.uk (Gavin Henry)

References:
- ATT NOC
  - From: ghenry at suretec.co.uk (Gavin Henry)
- ATT NOC
  - From: nimrodl at gmail.com (Nimrod Levy)
- ATT NOC
  - From: ghenry at suretec.co.uk (Gavin Henry)
- ATT NOC
  - From: nimrodl at gmail.com (Nimrod Levy)

Prev by Date: ATT NOC
Next by Date: TWCC engineer lurking?
Previous by thread: ATT NOC
Next by thread: ATT NOC
Index(es):
- Date
- Thread