Re: [j-nsp] Juniper MX5 Advice

Hi Jason, If having everything in your network going to one MX5 feels less than ideal, than you could do 2 VRRP instances, with each MX5 being the priority router for one of the VRRP instances. Then have half of your network default to the virtual-address of one VRRP instance, and the other

Re: [j-nsp] eBGP with internet provider from DataCenters

Hi Yham, FYI - I think one of my email messages on this thread didn't go out, the body of the message was larger than some threshold, and it requires a moderator approval. (they'll get to it at some point =-) can you comments on how AS-confederation will benefit more over having all BRs part

Re: [j-nsp] eBGP with internet provider from DataCenters

On 11/15/13 11:29 AM, Michael Hallgren wrote: Le 15/11/2013 17:10, Dave Curado a écrit : Hi Yham, Thanks for the map -- your situation is a lot more interesting than it first appeared! I agree! :-) I'm guessing there may be some number of requirements and policy decisions that went

Re: [j-nsp] eBGP with internet provider from DataCenters

Hi Yham, Thanks for the map -- your situation is a lot more interesting than it first appeared! I'm guessing there may be some number of requirements and policy decisions that went into this. Without knowing all the back story, it makes it a little tricky to say what would be best solution.

Re: [j-nsp] eBGP with internet provider from DataCenters

Hi Yham, On the Pro side, you would conserve one ASN by using the same ASN for both data centers. Also, if in the future the datacenters were to get some direct connectivity with each other, it would be relatively straight forward to join the network control planes together. I can't think of

Re: [j-nsp] eBGP with internet provider from DataCenters

Hi Yham, Ah. I assumed by your original question that the datacenters were not interconnected. It sounds like you should be able to call both your datacenters, together, a single AS. You'll want to create a full ibgp mesh, and routing should be relatively straight forward. HTHs, Dave On 1

Re: [j-nsp] VLAN-CCC: Protocol Connection

Another possible way to get the desired connectivity would be to create two VLANs to the customer (customer "A") and then create 2 CCC connections, one to customer "B" using VLAN 888 and another to customer "C" using VLAN 889 (or whatever). The thing to keep in mind about using VPLS is that (by

Re: [j-nsp] Interconection of Logical Systems or Routing Instances

Hi, You could do this... set logical-systems R1 interfaces lt-1/2/0 unit 1 encapsulation ethernet set logical-systems R1 interfaces lt-1/2/0 unit 1 peer-unit 2 set logical-systems R1 interfaces lt-1/2/0 unit 1 family inet address 100.100.100.1/24 and then set logical-systems R2 interfaces lt-1