7 comments on “Juniper powers LINX’s foray into 100G

  1. I guess one of the untested things regarding the PTX is whether it has the “Trig’s new broom” factor of the MX. Today’s MX is a totally different box from the launch platform, and has evolved there through piecemeal card upgrades leaving nothing but the chassis unchanged.

    Traditional thinking is that the core box of today moves out to the edge over time and becomes the edge box of tomorrow. If the PTX has the “Trigger” factor then it could find itself evolving with more and faster ports over time, allowing it to keep its place in the core rather than needing to move aside for the next generation…

    P.S. I think you may have meant “burst a dam” rather than “burst a damn” 😉

    • in my view the MX has moved in a certain direction inspite of Juniper not because of them. Many ISPs looked at it and thought, hmm I could do Internet cheaply on that box because I don’t need a lot of features – and it’s evolved to where it is now. PTX will only work of the competition can’t do a box at around the same price point with features, and ALU atleast seem to be getting very very close.

  2. A note from pedant’s corner – the Juniper LAN uses 195.66.224.0/25 rather than 195.66.224/5 as stated in your article.

    • A rebuttal from another pendant’s corner 😉

      The Juniper LAN used to be 195.66.224.0/23 (not /25) and has recently moved to a /22 mask.

      I have to admit that the use of 224/5 to indicate 224 and 225 caused me a moment of confusion too, but I never thought that Adam was implying a /5 network for the peering LAN, I just threw a type exception and retried the next overloaded definition if the ‘/’ operator…

  3. A rebuttal from another pendants corner 😉

    The Juniper LAN used to be 195.66.224.0/23 (not /25) and has recently moved to a /22 mask.

    I have to admit that the use of 224/5 to indicate 224 and 225 caused me a moment of confusion too, but I never thought that Adam was implying a /5 network for the peering LAN, I just threw a type exception and retried the next overloaded definition if the ‘/’ operator…

  4. I think I preferred the critique on damnation! My auto-correct obviously knows which word I use the most! But I didn’t spot John’s error, and I guess it goes to show we all know what we mean when we say LINX peering LAN or 195.66.22-something…

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s