[ietf86-tech] External configuration details for Brighthouse
Jim Martin
jim at daedelus.com
Sat Feb 23 20:07:26 PST 2013
Here are all the details for the router configs....
- Jim
Begin forwarded message:
> From: "Jenkins, Jelani K." <Jelani.Jenkins at mybrighthouse.com>
> Subject: RE: SRQ-887451 | Caribe Royal Dual Stack
> Date: February 23, 2013 8:01:39 PM PST
> To: Jim Martin <jim at daedelus.com>
>
> Hi Jim,
>
> It’s been a pleasure working with you so far. I’m glad that I’ve been involved. I have included BFD for BGP to my maintenance plan. BFD will be configured with an interval of 100ms x 4. I included this information with the circuit IDs to the below thread. I have also asked our team how and if they want to make adjustments to metrics for communities you send us. As this can be easily configured, it’s possibly that we can redesign a route policy, so that other customers can easily inherit a new set of route policies if needed. Otherwise, is it possible for you to add weight on your routers for those networks to prefer one path over another?
>
> Other than path selection, we are ready to proceed with this maintenance. Talk to you soon.
>
> Thank you,
>
> Jelani
>
>
> Jelani Jenkins
> Associate Operation Engineer III
> Bright House Networks
> Office: (813) 436-2700 ext. 74022
>
>
>
> From: Jenkins, Jelani K.
> Sent: Friday, February 22, 2013 2:19 PM
> To: 'Jim Martin'
> Subject: RE: SRQ-887451 | Caribe Royal Dual Stack
>
> Hi Jim,
>
> Regarding our discussion, I have constructed a maintenance to allow the below subnets to be advertised from your network. I will perform this maintenance tomorrow night. Our equipment will be performing BFD within OSPF between the two separate service edge routers. BFD is configured to detect a loss of connectivity within 400ms (roughly .5 second). Regarding your community string, your IPv4 routes will be tagged with community string 910:3001, and your IPv6 routes will be tagged with community string 910:13001. Per your request, we will only advertise full routes to your network. I’ve attached my contact information to this email if you need to reach me. If I am not available, you can reach our team at 866-477-1386. My hours are from 2:00 PM to 12:00 AM (Wed through Sat), but feel free to call me at anytime.
>
> On March 4th , the our circuit will be preconfigured, and our field tech will inform you which switch belongs to the subnets. We will also label the switches, so that you know which switch belongs to the subnets. Call me if you have any questions or concerns.
>
> · Bright House Contact Information:
> o Jelani Jenkins Contact # 813-382-3731 ext 74022
> o NOC Contact # 866-477-1386
> o Ticket #: SRQ-887451
> · BGP Information:
> o Our AS# 33363
> o IPv4 Community: 910:3001
> o IPv6 Community: 910:13001
> o BFD Interval: 100ms
> o BFD Multiplier: 4
> · IPv4 Address (Side A)
> o Circuit ID: I.00B81.002.002.1
> o Our address: 75.112.170.148/31
> o Your address: 75.112.170.149/31
> o IPv4 BGP Password: JHk3sld0932l
> · IPv6 Address (Side A)
> o Circuit ID: I.00B81.002.002.1
> o Network: 2605:a402:0:1::/64
> o Our address: 2605:a402:0:1::1/64
> o Your address: 2605:a402:0:1::2/64
> o IPv6 BGP Password: JHk3sld0932l
> · IPv6 Address (Side B)
> o Circuit ID: I.00B81.001.002.1
> o Network: 2605:a402:0:2::/64
> o Our address: 2605:a402:0:2::1/64
> o Your address: 2605:a402:0:2::2/64
> o IPv6 BGP Password: CGw29sadj9n1
> · IPv4 Address (Side B)
> o Circuit ID: I.00B81.001.002.1
> o Our address: 75.112.170.150/31
> o Your address: 75.112.170.151/31
> o IPv4 BGP Password: CGw29sadj9n1
> · Networks allowed to be advertised:
> o 130.129.0.0/16
> o 2001:df8::/32
> o 31.130.224.0/20
> o 31.133.128.0/18
> o 2001:67c:1230::/46
> o 2001:67c:370::/48
>
> Thank you,
>
> Jelani
>
>
> Jelani Jenkins
> Associate Operation Engineer III
> Bright House Networks
> Office: (813) 436-2700 ext. 74022
>
>
>
> From: Jenkins, Jelani K.
> Sent: Monday, February 18, 2013 9:24 AM
> To: 'jim at daedelus.com'
> Cc: Ickovic, Jeremy C.
> Subject: SRQ-887451 | Caribe Royal Dual Stack
>
> Hi Jim,
>
> I will be working with you to complete this request. I have attached my contact information to this email. I am in the process of installing the routes into RadB, but I’ve noticed the below routes are register with APNIC and does not reflect ownership to Caribe Royal. Can you print, complete, sign, and email the attached document to me, so that we can officially inject this routes into the RadB database? We are going to use /127 IPv6 addresses for the BGP peering. Let me know if you need something larger, such as a /64 range. I also wanted to have a conference call on Thursday at 2:30 PM to discuss the install process of this request. Let me know if you have any questions.
>
> 130.129.0.0/16
> 2001:df8::/32
> 31.130.224.0/20
> 31.133.128.0/18
> 2001:67c:1230::/46
> 2001:67c:370::/48
>
> Thank you,
>
> Jelani
>
>
> Jelani Jenkins
> Associate Operation Engineer III
> Bright House Networks
> Office: (813) 436-2700 ext. 74022
>
>
>
>
>
> 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/20130223/cc94ad07/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2603 bytes
Desc: not available
Url : http://www.daedelus.com/pipermail/ietf86-tech/attachments/20130223/cc94ad07/attachment-0001.jpg
-------------- 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/20130223/cc94ad07/attachment-0001.bin
More information about the ietf86-tech
mailing list