Talk:Juniper Networks

Small Request Edit

The current Lead contains the following text:

"Juniper grew to $673 million in annual revenues by 2000, challenging Cisco's once-dominant market-share in networking products."

In this discussion with @Thincat:, we seemed to agree on a slightly modified version with a specific date and market-share reference:

"Juniper grew to $673 million in annual revenues by 2000. By 2001 it had a 37 percent share of the core routers market, challenging Cisco's once-dominant market-share."<ref name="three"/>

Though I am making many other minor tweaks boldly in response to GA review feedback, because this content is about a competitor, I felt it would be more appropriate to use Request Edit. CorporateM (Talk) 21:52, 4 May 2015 (UTC)

Also, there are several errors in the following text, some of which were recently introduced by an IP here and some of which were my own errors

In October 2013, Juniper introduced another proprietary protocol network architecture called MetaFabric for a new set of switches, the QFX5100 family, that were needed to adopt the MetaFabric architecture.[119]

Corrections are as follows:

• The source says "networking architecture" as oppose to "networking protocol"
• Juniper said Metafabric is not "proprietary". Checking the source and doing a Google search seem to verify this. The only thing I found in a quick Google search is here where a Juniper spokesperson says it is not proprietary.
• The statement "not IETF or IEEE compliant..." is currently unsourced, but I did find a source for it not being TRILL compliant. The source says this is because Juniper is an advocate against TRILL (not really sure if any of this belongs on this page though, rather than a sub-page on Metafabric if one exists)
• I wrote "the QFX5100 family, that were needed to adopt the MetaFabric architecture", but the source just says "that is one of the foundations of the new architecture" not that the switch is required.

CorporateM (Talk) 22:43, 19 August 2015 (UTC)

• Those all look reasonable to me, so I implemented the edit request. Please check my work for errors. As always when I respond to edit requests, I take full responsibility for any changes I make. Also, I have no COI regarding Juniper or their competitors (The area of engineering I work in mostly involves microcontrollers that cost less than a dime -- the sort of thing you find inside toasters and children's toys). --Guy Macon (talk) 12:48, 20 August 2015 (UTC)

Thanks @Guy Macon:! Just one nit-pick. It seemed a bit awkward that it says Metafabric is "for" a set of switches. I double-checked the source and it doesn't look like it's built specifically for the switch. CorporateM (Talk) 14:35, 20 August 2015 (UTC)

Good point. What wor.ding would you suggest? --Guy Macon (talk) 17:19, 20 August 2015 (UTC)

@Guy Macon: "MetaFabric for and a new set of switches" CorporateM (Talk) 17:24, 20 August 2015 (UTC)

Done. --Guy Macon (talk) 17:36, 20 August 2015 (UTC)

I researched through the Juniper equipment documentation and I have not found any Juniper equipment that is capable of IEEE 802.1aq shortest path bridging. 166.173.249.212 (talk) 22:47, 23 August 2015 (UTC)

References

List of acquisitions by Juniper Networks

FYI - I've posted a suggestion that we re-purpose the well-sourced summary of Juniper's acquisition history from this article to the sub-article, as suggested by WP:Summary style for sub-articles. CorporateM (Talk) 20:24, 27 May 2015 (UTC)

Comments on the article

I read the article and I have a few comments.

1. Most of the references to Juniper Networks and Cisco Systems only use the first part of the name of the companies. I fixed the introduction and the next two paragraphs but then I stopped because the amount of fixing is rather large.

2. Internet is a proper word and needs to be capitalized. I see many instances of it that are not capitalized and need to be fixed. I fixed a few but, again, more need to be fixed.

3. Some information about the crash of the company stock after 2000 should be included in the article.

4. "Juniper promoted its products as stable enough to make IT staff bored and Cisco announced lab tests from Light Reading proved its products were superior to Juniper, whereas the publication itself reached the opposite conclusion." I don't understand this sentence. It seems contradictory and illogical.

ICE77 (talk) 05:01, 16 November 2016 (UTC)

O/S Linux based system

To understand the Juniper Networks system architecture in principle, Would it be ok to write the Juniper Device is based on O/S Linux based system? Goodtiming8871 (talk) 11:56, 14 November 2017 (UTC)