Re: [j-nsp] Standard practice for customer eBGP peering traffic engineer

2017-11-14 Thread Hugo Slabbert 


On Mon 2017-Nov-13 15:27:36 +, Nick Cutting  wrote:

What is the benefit for a customer or a provider in doing this v.s just 
the customer prepending their own AS?


Prepending done customer side would be visible to anyone beyond that first 
BGP peering between the customer and provider, including any of the 
provider's other BGP customers.


Generally, these provider prepend communities would be targeted for 
external relationships.  So, example would be that you want to have 
provider X's customers send to you directly via provider X, but provider 
X's peering sucks so you want anyone who is *not* a direct customer of 
provider X to avoid routing through provider X.


--
Hugo Slabbert   | email, xmpp/jabber: h...@slabnet.com
pgp key: B178313E   | also on Signal


signature.asc
Description: Digital signature
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Enhanced MX480 Midplane?

2017-11-14 Thread Tobias Heister 

Hi,

Am 14.11.2017 um 13:27 schrieb Sebastian Becker:

The enhanced midplane allows you already to use higher bandwidth with redundancy at 
least on the MX960. 205G per slot (not > enhanced) against 240G per slot (enhanced) 
So if you want to use a MPC5E-100G10G and populate every port (2x100G plus 4x10G) > 
you need the enhanced midplane and the SCBE2. Same for the MPC5E-40G10G and the 
Q-Versions of these cards. Otherwise you > overbook the midplane.


Funny enough the MPC7 has no reduced Bandwidth with the non enhanced Midplane, 
so for now only MPC4/5 suffer from that old midplane. I always wondered why 
that is the case. Might be a combination of PFE/Trio Generation and 
frequency/speed per Serdes to Fabric connectivity. If somebody knows the 
details i am eager to know.

We will see what SCBE3 might bring there (other than allowing us to run MPC7 at 
full speed with redundancy and pave the way for future MPC)

--
Kind Regards
Tobias Heister
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Enhanced MX480 Midplane?

2017-11-14 Thread Daniel Roesen 
On Tue, Nov 14, 2017 at 08:55:03PM +0100, Pavel Lunin wrote:
> > Is there anyone who can give more details about the enhanced midplane?
> 
> It's just more lines (wires) to provide more fabric bandwidth per-slot/PFE.
> And maybe more power as well, I am not sure though.

No, it's just better quality multipin connectors for the fabric lanes so
they can run at a higher frequency without too much
damping/crosstalk/reflection/whatevertheproblemactuallywas.


Best regards,
Daniel

-- 
CLUE-RIPE -- Jabber: d...@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Enhanced MX480 Midplane?

2017-11-14 Thread Pavel Lunin 
Is there anyone who can give more details about the enhanced midplane?
>

It's just more lines (wires) to provide more fabric bandwidth per-slot/PFE.
And maybe more power as well, I am not sure though.

It's been shipping for ages (since 2012 or something like). It had been
supposed to be required even for SCBE and MPC3 non-NG but then Juniper
thought twice and finally it was not really necessarily until MPC5. See
Sebastian's comment for what it it gives in terms of bandwidth per slot.

So, in theory, all MX240/480/960 have been shipped with enhanced midplane
for many years, if only your partner/SE, or whoever makes the specs, does
his job well or you don't specifically ask for the non-enhanced version for
some reason (if it's still not EOL, I don't remember).

You can check whether you have it with the following command:

user@mx480> show chassis hardware | match Midplane
Midplane REV 04   750-047862     Enhanced MX480
Midplane

In the specs this is referred as MX480-BASE3 or -PREMIUM3 in contrast to
-BASE or -PREMIUM for non-enhanced midplane. You normally don't buy a
chassis on its own, so you don't see part codes like CHAS-BP3-MX480-S in
your BOMs.

AFAIR, you can also buy the new midplane as an FRU and change it yourself
though it requires to get all the cards out of the box.

--
Pavel
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Enhanced MX480 Midplane?

2017-11-14 Thread Sebastian Becker 
The enhanced midplane allows you already to use higher bandwidth with 
redundancy at least on the MX960. 205G per slot (not enhanced) against 240G per 
slot (enhanced) So if you want to use a MPC5E-100G10G and populate every port 
(2x100G plus 4x10G) you need the enhanced midplane and the SCBE2. Same for the 
MPC5E-40G10G and the Q-Versions of these cards. Otherwise you overbook the 
midplane.

— 
Sebastian Becker


> Am 14.11.2017 um 11:38 schrieb Olivier Benghozi :
> 
> 
> While I don't care about SONET/SDH in 2017 (sorry...), the enhanced midplane 
> (in the MX240/480/960 MX generation) also (mainly?) allows more bandwidth per 
> slot with the future SCBE3.
> You may find a fugitive Juniper 2016 PDF on your preferred search engine 
> ("SCBE3" "premium3" "mx").
> 
>> On 14 nov. 2017 at 09:56, Karl Gerhard  wrote :
>> 
>> this article is mentioning an enhanced MX480 midplane. This is the first 
>> time I hear of that: CHAS-BP-MX480-S (=Non-Enhanced) vs. CHAS-BP3-MX480-S 
>> (=Enhanced)
>> https://www.juniper.net/documentation/en_US/release-independent/junos/topics/concept/scbe2-mx480-desc.html
>> 
>> Is there anyone who can give more details about the enhanced midplane?
>> As far as I understand the cross-coupling of clock input is only related to 
>> SONET/SDH stuff, is that correct?
> 
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Enhanced MX480 Midplane?

2017-11-14 Thread Olivier Benghozi 
While I don't care about SONET/SDH in 2017 (sorry...), the enhanced midplane 
(in the MX240/480/960 MX generation) also (mainly?) allows more bandwidth per 
slot with the future SCBE3.
You may find a fugitive Juniper 2016 PDF on your preferred search engine 
("SCBE3" "premium3" "mx").

> On 14 nov. 2017 at 09:56, Karl Gerhard  wrote :
> 
> this article is mentioning an enhanced MX480 midplane. This is the first time 
> I hear of that: CHAS-BP-MX480-S (=Non-Enhanced) vs. CHAS-BP3-MX480-S 
> (=Enhanced)
> https://www.juniper.net/documentation/en_US/release-independent/junos/topics/concept/scbe2-mx480-desc.html
> 
> Is there anyone who can give more details about the enhanced midplane?
> As far as I understand the cross-coupling of clock input is only related to 
> SONET/SDH stuff, is that correct?

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Enhanced MX480 Midplane?

2017-11-14 Thread Patrick Okui 

On 14 Nov 2017, at 11:56 EAT, Karl Gerhard wrote:


As far as I understand the cross-coupling of clock input is only 
related to SONET/SDH stuff, is that correct?


Not just SDH. SyncE allows you to do frequency synchronisation of clocks 
over Ethernet transport.


http://grouper.ieee.org/groups/1394/c/20031216/Sync_Ethernet_039a_draft.pdf

Also look at the 1588 PTP documentation.

Useful for e.g LTE backhaul, or any scenario where centralised clocking 
is important.


--
patrick
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Enhanced MX480 Midplane?

2017-11-14 Thread Nathan Ward 

> On 14/11/2017, at 9:56 PM, Karl Gerhard  wrote:
> 
> As far as I understand the cross-coupling of clock input is only related to 
> SONET/SDH stuff, is that correct?


Probably 1588 and stuff as well. Useful if you’re a mobile operator or someone 
else that cares about accurate clocking for whatever reason.

--
Nathan Ward

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] Enhanced MX480 Midplane?

2017-11-14 Thread Karl Gerhard 
Hello

this article is mentioning an enhanced MX480 midplane. This is the first time I 
hear of that: CHAS-BP-MX480-S (=Non-Enhanced) vs. CHAS-BP3-MX480-S (=Enhanced)
https://www.juniper.net/documentation/en_US/release-independent/junos/topics/concept/scbe2-mx480-desc.html

Is there anyone who can give more details about the enhanced midplane?
As far as I understand the cross-coupling of clock input is only related to 
SONET/SDH stuff, is that correct?

Regards
Karl
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp