[ietf86-tech] Fwd: URGENT: Brighthouse issues with IETF
Jim Martin
jim at daedelus.com
Thu Mar 7 07:28:39 PST 2013
FYI ... Here's the guy with clue that called me...
- Jim
Begin forwarded message:
> From: "Brabble, Kerry D." <Kerry.Brabble at mybrighthouse.com>
> Subject: RE: URGENT: Brighthouse issues with IETF
> Date: March 7, 2013 10:26:57 AM EST
> To: "jim at daedelus.com" <jim at daedelus.com>
>
> Jim,
>
> As we discussed on the phone, the v6 issue should be resolved. I have verified that your prefix (2001:df8::/32) is now being properly exported at our border routers. I have also verified that both Level3 and TWC are accepting the route from us.
>
> I will dig into the v4 issues and get back to you shortly. My contact info is below if you need anything.
>
> -Kerry
>
>
> Kerry Brabble
> Principle Network Engineer
> Brighthouse Networks
> Sustaining Engineering
> Kerry.Brabble at mybrighthouse.com
> Office: 407-215-8114
> Cell: 813-230-9054
>
>
>
>
>
> On 3/7/13 6:51 AM, "Jim Martin" <jim at daedelus.com> wrote:
>
>> Ed,
>> Thanks very much! The three main contacts on our side would be:
>>
>> Jim Martin jim at daedelus.com +1 408 799-2788
>> Warren Kumari warren at kumari.net +1 571 969-4367
>> Collin Doyle cdoyle at verilan.com +1 503 810-2129
>>
>> - Jim
>>
>> On Mar 7, 2013, at 9:45 AM, "Mallette, Edwin J."
>> <edwin.mallette at bhnis.com> wrote:
>>
>>> Jim,
>>>
>>> We've got our senior folks working on this. Let me see if I can get
>>> them to loop you in directly.
>>>
>>> Ed
>>>
>>> On 3/7/13 6:41 AM, "Jim Martin" <jim at daedelus.com> wrote:
>>>
>>>> Ed,
>>>> We're still stuck in a hold on this. How is the escalation going?
>>>>
>>>> - Jim
>>>>
>>>> On Mar 6, 2013, at 8:39 PM, Jim Martin <jim at daedelus.com> wrote:
>>>>
>>>>> Thanks very much. We are really in a spot here, and we'd be happy
>>>>> to work this evening or first thing in the morning. Don't be shy
>>>>> about using my or Warren's cell.
>>>>>
>>>>> -Jim
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On Mar 6, 2013, at 8:22 PM, "Mallette, Edwin J."
>>>>> <Edwin.Mallette at bhnis.com> wrote:
>>>>>
>>>>>> Jim,
>>>>>>
>>>>>> My apologies, I'm escalating internally to get some additional
>>>>>> help here.
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Ed
>>>>>>
>>>>>> On 3/6/13 5:17 PM, "Jim Martin" <jim at daedelus.com> wrote:
>>>>>>
>>>>>>> Ed and Jeremy,
>>>>>>> We've had a really rough day with runaround at Brighthouse today.
>>>>>>> The
>>>>>>> links physically came up yesterday, however we've now been
>>>>>>> fighting for
>>>>>>> 24 hours with reachability issues with v4 and a total lack of v6.
>>>>>>> We've
>>>>>>> been getting full routes, and have been advertising all the IETF
>>>>>>> routes, but none of the v6 routes are being propagated and the v4
>>>>>>> is going out through some subset of peers. The end result is a
>>>>>>> nearly unusable network.
>>>>>>>
>>>>>>> We've been advised that this is based around an internal
>>>>>>> policy of "validating" our routes, and as it stands we won't have
>>>>>>> real reachability until after 5pm tomorrow.
>>>>>>>
>>>>>>> Note also that we've been working with Jelani Jenkins, who has
>>>>>>> done his best to help, but keeps running into roadblocks.
>>>>>>>
>>>>>>> This is putting the delivery of the IETF network in jeopardy,
>>>>>>> and seems almost entirely to be an administrative snafu. Could
>>>>>>> you please step in and help get this resolved? If you need any
>>>>>>> details to help, please contact me at +1 408 799-2788 at any time
>>>>>>> of day. If I'm not available, Warren Kumari is available to work
>>>>>>> on this as well at +1 571 969-4367.
>>>>>>>
>>>>>>> Thanks for your help!
>>>>>>>
>>>>>>> - Jim
>>>>>>>
>>>>>>> On Jan 15, 2013, at 2:56 PM, Jim Martin <jim at daedelus.com> wrote:
>>>>>>>
>>>>>>>> Great! Forgive my being so pedantic, but these are often areas
>>>>>>>> where we have issues.
>>>>>>>>
>>>>>>>> I'll get all my addressing and AS information to you shortly.
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> - Jim
>>>>>>>>
>>>>>>>> On Jan 15, 2013, at 11:51 AM, "Mallette, Edwin J."
>>>>>>>> <edwin.mallette at bhnis.com> wrote:
>>>>>>>>
>>>>>>>>> Jim,
>>>>>>>>>
>>>>>>>>> We have complete electronic diversity. We have active gear at
>>>>>>>>> the site but it is not the equipment we will be utilizing to
>>>>>>>>> provide service for the IETF and IEEE meetings. The circuits
>>>>>>>>> go back to different routers and the POP routers are in
>>>>>>>>> different cities - one will be in Orlando the other POP router
>>>>>>>>> will be in Tampa.
>>>>>>>>>
>>>>>>>>> The only issues we typically have with providing full tables
>>>>>>>>> for
>>>>>>>>> v4
>>>>>>>>> and v6
>>>>>>>>> tend to be related to the customer routers memory. As you do
>>>>>>>>> this regularly I don't foresee any issues there. We plan to
>>>>>>>>> offer you a pair of /30 IPv4 networks a pair of /64 IPv6
>>>>>>>>> networks for point-to-point to the two POP routers and then
>>>>>>>>> we'll re-advertise your networks.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Ed
>>>>>>>>>
>>>>>>>>> On 1/15/13 2:45 PM, "Jim Martin" <jim at daedelus.com> wrote:
>>>>>>>>>
>>>>>>>>>> Ed,
>>>>>>>>>> Yes, 1G is fine. Usually delivered on SX if you've got active
>>>>>>>>>> gear at the site. Can you confirm that the two circuits will
>>>>>>>>>> be physically and logically diverse? We just need to make
>>>>>>>>>> sure they're going back to different routers at different
>>>>>>>>>> sites, and that there's no common equipment and minimal
>>>>>>>>>> commonality of path (though the last leg into the hotel is
>>>>>>>>>> likely going to be common).
>>>>>>>>>>
>>>>>>>>>> Any issue with providing full tables for both v4 and native
>>>>>>>>>> (not-tunneled) v6?
>>>>>>>>>>
>>>>>>>>>> If there are any details I can get from you when I'm onsite
>>>>>>>>>> later this week, I'm happy to do so!
>>>>>>>>>>
>>>>>>>>>> Thanks!
>>>>>>>>>>
>>>>>>>>>> - Jim
>>>>>>>>>>
>>>>>>>>>> On Jan 15, 2013, at 11:23 AM, "Mallette, Edwin J."
>>>>>>>>>> <edwin.mallette at bhnis.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Jim,
>>>>>>>>>>>
>>>>>>>>>>> We can support either. We were informed early on that we
>>>>>>>>>>> might need to be ready to go higher than 1G, but if 1G is
>>>>>>>>>>> sufficient we can readily support that.
>>>>>>>>>>>
>>>>>>>>>>> I don't know that we need anything additional from you to
>>>>>>>>>>> make ready on our side. We'll need to share the logical
>>>>>>>>>>> details (such as what
>>>>>>>>>>> IPv4/IPv6
>>>>>>>>>>> point-to-point networks we're providing) AS number, peering
>>>>>>>>>>> router addresses etc, but for the order processing to get the
>>>>>>>>>>> UNIs delivered we should be fine though Jeremy can correct
>>>>>>>>>>> me if I'm wrong here.
>>>>>>>>>>> What
>>>>>>>>>>> interfaces media do you prefer ? TX, SX, LX ?
>>>>>>>>>>>
>>>>>>>>>>> Ed
>>>>>>>>>>>
>>>>>>>>>>> On 1/15/13 12:50 PM, "Jim Martin" <jim at daedelus.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Ed and Jeremy,
>>>>>>>>>>>> Nice to meet you both, and thanks in advance for your help
>>>>>>>>>>>> on these circuits. The install deadline on the circuits is
>>>>>>>>>>>> March 1st.
>>>>>>>>>>>> We'll
>>>>>>>>>>>> have
>>>>>>>>>>>> staff onsite starting the 5th, with the network going
>>>>>>>>>>>> "production"
>>>>>>>>>>>> on
>>>>>>>>>>>> the
>>>>>>>>>>>> 9th, and staying in production until the 24th. While 10G is
>>>>>>>>>>>> cool, it would require us to acquire some different
>>>>>>>>>>>> equipment for our border routers. We'll do that though if
>>>>>>>>>>>> it's important to you. Our general use case is 5 minute
>>>>>>>>>>>> peaks in the 350-500M range, with very rare spikes to 700M.
>>>>>>>>>>>> Usually, 2 x 1G is more than enough. The part that's
>>>>>>>>>>>> important though are that the circuits are as divergent as
>>>>>>>>>>>> possible (both physically and topologically)and that we can
>>>>>>>>>>>> get full IPv4 and
>>>>>>>>>>>> IPv6
>>>>>>>>>>>> BGP
>>>>>>>>>>>> feeds.
>>>>>>>>>>>>
>>>>>>>>>>>> As for my site visit, what info do you need for the Z end to
>>>>>>>>>>>> get your order in?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>
>>>>>>>>>>>> - Jim
>>>>>>>>>>>>
>>>>>>>>>>>> On Jan 15, 2013, at 7:31 AM, "Mallette, Edwin J."
>>>>>>>>>>>> <edwin.mallette at bhnis.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Jim,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Nice meeting you. I've CC-ed Jeremy who is in charge of
>>>>>>>>>>>>> the service delivery to the site. We are preparing to
>>>>>>>>>>>>> offer either a pair of 1G or 10G UNIs. What is your
>>>>>>>>>>>>> timeframe for the circuit activation (I.e.
>>>>>>>>>>>>> When
>>>>>>>>>>>>> will you have equipment in place so we can ensure our
>>>>>>>>>>>>> timeframes line
>>>>>>>>>>>>> up?)
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Ed
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 1/14/13 3:58 PM, "Jim Martin" <jim at daedelus.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Jason,
>>>>>>>>>>>>>> Thanks! I'll work with Ed to make this happen...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Ed,
>>>>>>>>>>>>>> Nice to meet you, I'm Jim Martin with the IETF NOC. As I
>>>>>>>>>>>>>> understand it, BrightHouse is providing two divergent 1G
>>>>>>>>>>>>>> links to the meeting, delivering both IPv4 and IPv6
>>>>>>>>>>>>>> transit. We have our own AS and address space, and will
>>>>>>>>>>>>>> be providing our own CPE (a pair of Juniper routers).
>>>>>>>>>>>>>> Also, I'm heading to the Caribe Royal for a site visit
>>>>>>>>>>>>>> later this week.
>>>>>>>>>>>>>> I'd like to work with you on the exact details of the
>>>>>>>>>>>>>> circuits, and any site specific information you might
>>>>>>>>>>>>>> need me to collect.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Looking forward to working with you!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - Jim
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Jan 14, 2013, at 12:15 PM, "Livingood, Jason"
>>>>>>>>>>>>>> <Jason_Livingood at cable.comcast.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The contact is Ed Mallette <Edwin.Mallette at bhnis.com>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 1/14/13 3:04 PM, "Ray Pelletier" <rpelletier at isoc.org>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> All;
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Do you have a POC with BrightHouse for Jim with regard
>>>>>>>>>>>>>>>> to the circuits?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Ray
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ________________________________
>>>>>>>>>>>>>
>>>>>>>>>>>>> CONFIDENTIALITY NOTICE: This e-mail may contain information
>>>>>>>>>>>>> that is privileged, confidential or otherwise protected
>>>>>>>>>>>>> from disclosure. If you are not the intended recipient of
>>>>>>>>>>>>> this e-mail, please notify the sender immediately by
>>>>>>>>>>>>> return e-mail, purge it and do not disseminate or copy it.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ________________________________
>>>>>>>>>>>
>>>>>>>>>>> CONFIDENTIALITY NOTICE: This e-mail may contain information
>>>>>>>>>>> that is privileged, confidential or otherwise protected from
>>>>>>>>>>> disclosure.
>>>>>>>>>>> If
>>>>>>>>>>> you
>>>>>>>>>>> are not the intended recipient of this e-mail, please notify
>>>>>>>>>>> the sender immediately by return e-mail, purge it and do not
>>>>>>>>>>> disseminate or copy it.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ________________________________
>>>>>>>>>
>>>>>>>>> CONFIDENTIALITY NOTICE: This e-mail may contain information
>>>>>>>>> that is privileged, confidential or otherwise protected from
>>>>>>>>> disclosure.
>>>>>>>>> If
>>>>>>>>> you
>>>>>>>>> are not the intended recipient of this e-mail, please notify
>>>>>>>>> the sender immediately by return e-mail, purge it and do not
>>>>>>>>> disseminate or copy it.
>>>>>>
>>>>>>
>>>>>> ________________________________
>>>>>>
>>>>>> CONFIDENTIALITY NOTICE: This e-mail may contain information that
>>>>>> is privileged, confidential or otherwise protected from
>>>>>> disclosure. If you are not the intended recipient of this e-mail,
>>>>>> please notify the sender immediately by return e-mail, purge it
>>>>>> and do not disseminate or copy it.
>>>>
>>>
>>>
>>> ________________________________
>>>
>>> CONFIDENTIALITY NOTICE: This e-mail may contain information that is
>>> privileged, confidential or otherwise protected from disclosure. If
>>> you are not the intended recipient of this e-mail, please notify the
>>> sender immediately by return e-mail, purge it and do not disseminate or copy it.
>>
>
>
> ________________________________
>
> CONFIDENTIALITY NOTICE: This e-mail may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient of this e-mail, please notify the sender immediately by return e-mail, purge it and do not disseminate or copy it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.daedelus.com/pipermail/ietf86-tech/attachments/20130307/7dcfc293/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://www.daedelus.com/pipermail/ietf86-tech/attachments/20130307/7dcfc293/attachment-0001.bin
More information about the ietf86-tech
mailing list