Marvell to Add Innovium to Its Portfolio to Enhance High-End DC Switching

On August 3rd, Marvell announced its planned acquisition of Innovium for $1.1B.  The addition has good synergies.  Innovium had several design wins in the hyperscaler segment and Marvell provides additional scale, desire to expand custom, semi-custom, and merchant networking offerings in the Cloud.  While the deal is pending regulatoriy approval with a planned close date by the end of 2021, we do not see any impediments to the deal closing or being delayed. 

We have been tracking merchant silicon performance for over four years and for the entire 12.8 Tbps sampling and production curve and see many positives to this deal. The current state of 12.8 Tbps in 2021 remains the tale of two sets of customers.  Over 1M ports of 400 Gbps a quarter ship into three hyperscalers in each quarter already.

These customers use a mix of copper and fiber, and Innovium’s market share is impressive as a challenger to Broadcom.  The rest of the market is mainly in trials, delayed by COVID-19 and multiple semiconductor shortages.  As the market moves to mainstream 12.8 Tbps adoption, those three hyperscalers will move to 25.6 Tbps, a chip that Innvoium is currently sampling.

This market dynamic creates an opportunity for Marvell.  Not only are there synergies, but Marvell obtains a more substantial portfolio for what lies ahead in networking (chiplets, onboard optics, and silicon photonics) and back-to-back opportunities to win ASIC share.  Marvell’s recent product announcements and Inphi acquisition highlight several go-to-market opportunities and new scale as a data center supplier that Innovium can now participate in.

650 Group's early hyperscaler executive leadership interviews indicate positive feedback regarding  the announced deal.  While this is a consolidation amongst ASIC suppliers, we view the long-term state of Marvell with Innovium as leading to more OEM/ODM ASIC choices and increased innovation and R&D for this market.  The deal paves the way for the market to be more robust when we discuss 51.2 Tbps which is not that far out.  It’s important to note that the future state of data center switching involves significant innovation and increasing importance inside the data center.  Ethernet switches will be critical to deploying AI/ML and other future workload technologies to move beyond plumbing to a key interconnect technology.


Turning to vendors, we see an increased interest in using ASICs as a way to differentiate product offerings, and our OEM/ODM interviews indicate a similarly positive view of this announcement. Product launches in 1H21 were slow as vendors took a conservative approach to launch new products and not ship.  We view the timing as suitable for OEM/ODM as they look to early 2022 for new product launches.

We look forward to learning more when the deal closes and during Marvell’s analyst day later this year.

- Alan Weckel, Founder and Technology Analyst at 650 Group.

On April 21, 2021, DISH, the fourth wireless operator in the US market, and hyperscaler Amazon Web Services (AWS) announced plans to work together, whereby DISH will leverage AWS infrastructure and services to build a cloud-based 5G Open Radio Access Network.   The DISH/AWS announcement is important because this is the first 5G Radio/hyperscaler deal – or second if you count Rakuten as a hyperscaler.  We are encouraged by the DISH/AWS deal and think this represents a big step in the industry.  What’s so important is that two of the three major Radio Access Network (RAN) functions will be running on AWS; these are the Centralized Unit (CU) and the Distributed Unit (DU).  We see the DU running on the AWS service called Outposts as being the most critical part of this announcement, because historically this hardware has been delivered as a proprietary hardware system using proprietary semiconductors from the likes of vendors like Ericsson, Nokia and Huawei.  Thus, AWS’ involvement in the DISH network serves as a reminder of the opportunity for RAN vendors to deploy cloud native RAN in future cellular network deployments.

DISH is employing a terminology it called a “Capital Light” model, whereby it reduced the amount of capital spending it requires to build out its planned national network.  Key to achieving this light capital model is leveraging the capital spending done by AWS and instead leveraging what some might call an OPEX oriented model.  DISH plans to launch live cellular services in Las Vegas, NV first, and then its 5G network will cover 20% of the US population by June 2022 and then 70% by June 2023 and 75% of by June 2025, and thereafter it will continue its build to “match competitors beyond 2025.”  The company also plans to begin building enterprise focused 5G networks beginning in 2021.

In our follow-up inquiries to the AWS and DISH teams, we have learned that DISH is exercising an option to run O-RAN using AWS Graviton hardware plus Enterprise Kubernetes Services.  Additionally, DISH has the option to use Intel based COTS based hardware in parts of its network.  Thus, DISH has flexibility to deploy baseband systems on AWS or in its network, and can use Graviton or Intel systems.   We have seen AWS engage in contracts with other parties where there are minimum usage rates or dollar commitments.  We are not sure this is the case for the DISH deal, but AWS explains that it expects to deliver “thousands of site specific hardware,” while at the same time DISH expects that by mid 2023, it will have built out “15,000 cellular sites.”

We wanted to share some insights on how this relationship appears to be structured.  It appears that many scenarios have been envisioned as to how the relationship may evolve in the future, and we think that both parties have worked in contract terms that allow some flexibility in achieving each company’s goals.  We did not review the contract between the two companies, but in a webinar presentation held April 30, 2021, executives from DISH hedged their bets somewhat on the relationship with AWS in ways we found interesting:

• DISH is building an architecture on top of AWS that will address potential down-time that may occur at AWS.  AWS said it has designed its system to route around failures such as fiber cuts; it appears that DISH is not going to rely completely on the AWS redundancy features alone. 
• DISH is maintaining its current working relationship with Intel, which began a year ago.  DISH explains that it its first wave of network buildouts, it has been using Intel FlexRAN components in building its 4T4R network.  DISH explains that its 4T4R network requires only “moderate compute” capabilities and that FlexRAN from Intel is sufficient for that.  But for its planned Massive MIMO Open RAN systems, it will need a new generation of acceleration.  DISH claims that it is maintaining a dialogue with Intel about these future requirements.  However, AWS executives explained that the RAN DU function will be running on AWS Outposts services, and in particular the 1U version that uses the AWS in-house developed ARM-based Graviton2 processors.  Additionally, AWS explained that “obviously we’re working with accelerator cards.  It also explained that “Intel remains a very good partner and we expect to work with Intel.”  We hone in on this topic because up till now, every Open RAN system we are aware of has used x86 and for all but the lowest throughput systems uses some type of acceleration like FPGA cards.  It seems that AWS would prefer DISH to use Graviton2 Outposts, but DISH is keeping its options open in case its Massive MIMO systems don’t work well with Graviton2.
• Enterprise 5G deployments might not use AWS hardware and services exclusively.  DISH executive Marc Rouanne explained that “some customers may demand we put our software to other hardware.”
• DISH will maintain its use of VMWare at least in part.  Although DISH has selected vendors that offer software systems that are cloud-native, which in the context of the presentation meant container and Kubernetes based, there are some network functions that are not cloud-native.  For those functions that are not cloud-native, DISH explained that it will use VMWare to manage these systems (we interpret this as meaning Virtual Network Functions).   Additionally, VMWare capabilities are being used “across the board” as a minimum to help onboard and test Containerized Network Functions (CNF).  And, VMWare will be used to support enterprise customers who require VMWare functionality.  Also, DISH said it was a very important requirement that AWS and VMWare works together, because DISH will “used VMWare on top of AWS services,” which could mean a lot of things, but in context, we think it means that VNFs will run on VMWare in the AWS computing environment.

In a briefing with Rakuten Mobile today, we learned two neat things:  It is experimenting with 3GPP on satellite, and it hopes to announced a full-stack Rakuten Communications Platform (RCP) customer as early as next quarter.  The company also shared some plans that it has for improving coverage to 96% by the end of the summer '21, and that it believes it has a 50% total cost of ownership advantage for its 5G infrastructure versus a traditional network operator.

So, what's so important about "3GPP on satellite?"  If satellites are able to communicate with all cell phones and other cellular devices, this would mean that coverage could be enabled where we might need to have placed macro base stations.  If we don't need macro base stations everywhere as satellites provide that coverage in sparse areas, or maybe even along highway routes, then a future cellular operator might be able to build its network with far fewer macro towers and rely more on a "barbell" approach, with small cells providing high throughput in busy areas and satellites providing coverage between busy areas.  This would reduce demand for 5G base stations.  Rakuten expects that its satellite partner, AST, may offer satellite coverage for Japan at the end of 2023 or the beginning of 2024 - that is a ways off.  But, this means that in 3 or so years, the need for base stations may be considerably reduced.

Also, Rakuten spokesperson, Tareq Amin, said he thinks it is possible that Rakuten may announce its first RCP customer as early as next quarter.  We published about RCP in November 2020, around when the team first started making RCP known to the public.  This means that a division of a mobile operator, Rakuten Mobile, may be selling its know-how, technology and services to another telecom operator, presumably outside of Japan.  This is a big deal in that most operators buy from vendors and systems integrators, not from others who are in the same business as them.  It is also a big deal because cloud companies like Amazon, Microsoft and Google all want to sell their cloud services to operators, too.  And, if RCP gets there first, and sells its full stack (radio, core, billing, orchestration, OSS) it would represent a first-ever full stack services deal.  

Disaggregation has been around in the networking space for nearly a decade, especially in hyperscalers data center Ethernet Switches.  The insatiable demand for bandwidth, control, and cost reductions drove the white box from the Google science project to the dominant consumption model for Ethernet Switching in the hyperscalers.  The high-scale SP Router market has lagged.  Broadcom’s launch of Jericho gave the industry its first truly merchant ASIC, with companies like DriveNets providing the operating system, networking services and orchestration to create the compelling solution and ecosystem. 

Traditional Routing Doesn’t cut It
Up through and including the current generation of 100 Gbps based routers, the western market had to choose between three options (Cisco, Juniper, and Nokia), all vertically integrated with little flexibility other than a service provider having multiple vendors deployed to keep pricing pressure and innovation moving.  Cloud providers might have done the same thing; however, the price points, port density, and availability of products were not where they needed to be.  Can you imagine the Cloud today with 4-8 ports of 100G per box and $10,000 price points per port over millions of ports?  It just would not have worked financially or space/power-wise to continue down that path.  The Cloud, without legacy infrastructure, became a market dominated by ASIC capabilities and software, and branded system vendors have been playing catch-up ever since.

High-Scale Network Transformation to Disaggregation
As Telco SPs become more cloud-like in design and procurement and we enter the next wave of product availability, there is a tremendous opportunity for the high-scale router market to go through its own disaggregation transformation.  Our end-user interviews indicate a strong preference to move in this direction during the next two product upgrades (400 Gbps x56 Gbps SERDES and 400/800 Gbps x112Gbps SERDES).
While hyperscaler Cloud providers will fully embrace SP Router disaggregation with the 400 Gbps upgrade cycle starting next year, the rest of the Cloud and traditional SP industry is not that far behind.  Disaggregated routers with OS, ASIC, and optics purchased individually and potentially from multiple suppliers will become more common - both 1RU routers used at the edge as well as larger high-scale routers used for core and aggregration that are based on clusters of white boxes.

Disaggregated Routing Growth
We expect the market for Disaggregated Routing to grow substantially during the next several years as RFPs and plans turn into production traffic and revenue (Figure 1), replacing traditional routers.  Disaggregated routing and the consumption model associated with it will become a significant portion of the Router market over the next several years and create a significant opportunity for vendors that embrace the transformation.

Disaggregated Routing Market Players
Several vendors, including Cisco have entered the disaggregated routing space.  Another contender is DriveNets, a startup who’s software is used by AT&T to build a disaggregated core network. The highest-scale backbone in the US is now running on a disaggregated network model.

Facebook revenue grew robustly in 2Q20, and its CAPEX guidance remained consistent for 2020 compared to previous revisions in the last two quarterly results.

Facebook’s results were counter trend to our expectations that many advertisers would pull back spending do to COVID-19 based on lack of supply (no need to advertise consumer staples) or from consumer spending put on pause (cars that people don’t need while sheltering at home).  We believe Facebook benefited from more time on the platform and from the targeting of specific adds on areas of discretionary spending that did grow like sports equipment (good luck finding a bike, kayak, or other social distancing sports gear) and WFH (consumers shifting patterns of spending more for their residents while WFH or just making the home more comfortable due to extended hours in it).

Facebook, like Google, is under government scrutiny for its scale and size.  We are closely monitoring the trends of government oversight from the US government and well as other countries like Australia which is forcing Facebook to pay for news as well as Microsoft’s potential purchase of Tik Tok (as of writing this over the weekend, they were still pursuing them).  It seems like the duopoly here is not preferred by most governments at this stage and expect election results to polarize the losing party against social media companies into 2021.

Google, the largest US Hyperscaler by revenue, reported Search and Social results that declined Y/Y for the first time while IaaS revenue grew nearly $1B Y/Y.  We were a little surprised at Facebook’s robust growth compared to Google’s. Google’s results were in line with our overall expectations for Search and Social decline in 2020 as consumers and advertisers resetting to the new normal.  We expect more targeted ads throughout 2020 as consumers live and work from home, and many students live and study from home during the fall semester.

Google has made big bets and investments in IaaS, and we continue to see AI as an area where they will attack AWS and Azure.  It is unclear if IaaS is compatible with the culture withing Google, which could put an upper limit on the verticals and companies Google can sell to.  During 1H20, Google was surpassed by Amazon in our supply chain interviews as the company with the most influence on the technological direction of industry-wide future products. 

We see a passing of the guard as AWS CAPEX is now much higher than Google’s, and the supply chain sees Amazon as more significant revenue potential.  We expect this change to reverberate throughout the supply chain, primarily based on how each Cloud provider uses custom or semi-custom semiconductors in their data center infrastructure.  This is something we are happy to talk about as we prepare our 2Q20 results and our fall readouts.
-- Alan Weckel, Founding Analyst, 650 Group

Over the next five days, we will highlight each of the US Hyperscalers and the results they had during 1H20 and 2Q20. Today we will start with the overall trends in the market. US Hyperscaler revenue grew 20% in 2Q20 compared to a year ago, setting a new record.

US trade war activities, mainly against Huawei, caused significant lead time increases in many critical components for Cloud data center build-outs during the quarter as the 5G battle against China is having ripple effects into the Cloud supply chain. Custom ASIC and semi-custom ASIC development in the Cloud continue to expand with multiple new initiates around #AI #ML., #SmartNICs, accelerators, and #CPUs underway. This is not to mention Amazon Web Services (AWS) getting into #6G with a $10B investment in project #Kuiper for low earth satellites in direct competition with @SpaceX Starlink. There are over 50 custom ASIC projects in the Cloud. Each one has implications on the supply chain and immediate potential to shift market share from each Cloud provider.

Our overall projections for data center spend in switching, servers, and storage remain relatively unchanged since our previous forecast. Current results affirm our forecasts as we shift to vendor performance over the next two weeks, which we expect to be dependent on each company’s vertical and enterprise exposure.

We attended two separate presentations made by Ciena last week and have reflected on the comments made by the company.  In summary, Ciena advocated using both pluggables like ZR and ZR+  as well as high-performance optical transport systems (its main business) together to construct cost-effective networks.  The mix and match recommendation serves Ciena well, in that, substantially all of its revenues are high-performance systems, and coherent pluggables are a substitute threat to its business.  If its customer base wanted to adopt pluggables but continued buying systems from Ciena, it would be logical for the customers to consider both systems and pluggables.  Ciena argued that its pluggables would be superior to competitors, as well, highlighting its unique DSP, PIC and packaging as best in class.  We find the pitch could be compelling if Ciena’s pluggables are better, and would play to Ciena’s advantages.

Much of Ciena’s recent growth has come from cloud hyperscalers.  Hyperscalers currently use Ciena’s systems equipment for the Data Center Interconnect (DCI) use-case - to connect one data center to another.  We have forecasted that hyperscaler DCI networks will move rapidly towards coherent pluggables, once available, substituting for high-performance systems.  In Ciena’s presentation, it agreed with our assessment that short-haul DCI is the first place where pluggables will be put to work, displacing optical transport systems.  Our view is that, at the market level, the metro optical transport systems' revenue path in 2021 and beyond will decline based on the transition to pluggables-use by DCI networks.  Ciena is wisely hedging its bets by offering both pluggables and systems.  But, we don’t think pluggables-related revenues will offset the potential loss of systems revenue, especially if the move towards pluggables is fast.  One thing that Ciena has in its favor during this transition is it took first revenues on its 800 G class of systems equipment in its April 2020 fiscal quarter; its early 2020 launch could put Ciena back in the driver's seat again with customers who demand very high-performance optical links.  With the inclusion of 800 G systems, Ciena’s systems offerings will be more competitive than it was entering 2020, and more competitive than 400 G class of pluggables that are the primary topic of this article.  At present, only Ciena’s competitor, Infinera, has planned a 2020 launch of 800 G class of equipment.

Here are some specifics from Ciena’s two presentations (alternative link) last week. Ciena’s view is that single Span Data Center Interconnect (DCI) and High Capacity Access (Metro) are the most likely markets to adopt 400 Gbps ZR or ZR+ optical modules.  It says that multi-span metro may have some use for ZR/ZR+, and long-haul and subsea won’t leverage these pluggables in the near to medium term.  We agree with this assessment.  Ciena will be offering coherent pluggables in two ways, as part of its packet networking and optical systems portfolio, as well as offering them through its Microsystems business for use in 3rd party equipment.  

Ciena shared its assessment of its capacity versus reach comparison of its pluggables (56 GBd) and its high-performance systems (95 GBd).  In the capacity graph the company shared during its presentations, you can see that Ciena’s tests show that coherent pluggables generally have half the reach or half the speed.  The company advocates for “mixing bauds,” which means that for networks that are more complex than simple point to point DCI networks – for instance, ones that have lots of ROADMs, it makes sense to use high-performance metro DWDM systems as well as switches/routers with coherent pluggables.  By “mixing bauds,” Ciena says it expects to 100% coverage of complex metro/regional networks (typical of telcos).

The company explained that it uses four major components in making 400 G coherent pluggables:

• CMOS Technology node.  7nm finFET (35% the size of 28nm planar CMOS) 
• SiPhot PIC.  
• Advanced Packaging Technology.  Multi-die packaging.
• DSP.  Multiple FEC options.  Embedded CPU.  Client framing

At NetApp's analyst meeting today, CEO George Kurian sees opportunity in selling HCI (introduced F2Q18, 4-5 months ago), AFA, share-taking in SAN, and public cloud software and services.  Every large customer NetApp talks to, according to Kurian, is using multiple cloud service providers and/or SaaS services and most are using the hybrid cloud, which means using workloads both on the customer premises and public cloud.  According the company's marketing and sales executives, the company's sales and marketing strategy is focused on leveraging the company's entrance to the cloud services software market.

Substantial future announcements that were made by NetApp:

• In its nascent cloud-services software business, now being run by Anthony Lye, SVP Cloud Data services BU, the company set a target of reaching $400-600M of recurring revenue exiting its FY21 year - this effort to target cloud started over five years ago.    Additionally, this software is available at Microsoft Azure, Amazon Web Services and the company expects to announce other cloud service provider customers in the future.  Mr. Richard explains that the company's cloud software is "soon to be GA (general availability)."  Mr. Pasek guided that FY19 cloud data services is expected to reach $60M (see calculations below).
• NetApp will add NVMe and storage-class memory products in the future.  The company expects to disaggregate storage from the controller to build capable high performance systems using NVMe.

Summary of presentations
Joel Reich, EVP Products and Operations discussed trends in data center flash:
•             NVMe over Fabrics
•             Storage-class memory as cache
•             Persistent memory in server
•             Quad level cell NAND

Reich made some interesting comments:

• NetApp will add NVMe and storage-class memory in the future  
• Quad level cell NAND could spell the end of spinning disks
• In its most recent year, it had a 75% win rate versus DELL EMC

Brad Anderson, SVP and GM, Cloud Infrastructure BU, said that NetApp’s “Converged” (selling NetApp storage with non-NetApp servers) FlexPod business is now at a $2B run rate and >4,000+PB shipped.  The company recently initiated a Fujitsu partnership on March 26, 2018.  Anderson also said that NetApp’s Hyperconverged product, which has only been selling for the past 4-5 months, hit its financial targets in the first full quarter of shipments.  He also said that the HCI product is based upon on recently-acquired SolidFire technology and conceded that the company is hiring people with virtualization capabilities to further augment the product line.  HCI customers that were discussed during this presentation were:  ConsultelCloud (Austrialian SaaS company) and Imperva (security company).  

Anthony Lye, SVP Cloud Data services BU, joined a year ago and is responsible for the company’s efforts to build software that runs on and with public cloud services.  He describes this software as one that operates above the storage layer, to allow customers to manage their data, whether in cloud, SaaS applications or on premises.  It offers backup, disaster recovery, and for securing data, and then binds those services and data in context of applications and business policy using the orchestration Engine.  OnCommand is product name.  The underlying technology NetApp uses is called ONTAP Data Management, which Mr Lye explained was separated from its engineered systems (hardware) and port it to public clouds five years ago.  We remember when NetApp announced its plans to separate ONTAP as a software for the cloud at its analyst meeting a few years ago when Kurian took over as CEO.

Lye explained that “later this year,” NetApp will release cloud-based OnCommand performance management/monitoring tool to manage workloads in hybrid cloud environment. 

• Azure.  Microsoft Azure selected NetApp to become basis for its storage (in Azure console).  Lye says NetApp built Azure Microsoft files for them and we run it for them, paying on traditional subscription and consumption model.  Microsoft will include it in every enterprise service agreement and customer take-up has been beyond NetApp expectations.  Of multiple 100’s of preview customers, >70% are considered non-NetApp strategic customers (eg they are new customers).  NetApp software software royalties show up as an Azure line item in Azure bill. 
• AWS.  Available from NetApp on AWS services.  Shows up as AWS bill as NetApp billable item.
• Other Cloud Service Providers.  Expect to announce other relationships with other public clouds.

Lye said that NetApp’s cloud software business is expected to reach $400-600M of recurring revenue by end of FY21.

Henri Richard, EVP Worldwide Field and Customer Operations said "Cloud is soon to be GA.”  Richard explains this as its “Cloud Volume” product.  Richard explained that what is new this year is the hyperscaler relationships, starts a demand creation engine for the sales organization.  

Jean English, SVP Chief Marketing Officer said the company will focus on “cloud first” to reach new “global” buyers (e.g. multinational organizations), will lead with HCI and Cloud to enterprises.

Ron Pasek, EVP and CFO explains that FY18 is almost over and the company is beating FY18 plans (low-single digits growth), driven by flash.  The CFO said that the new accounting rule, ASC 606 impact to guidance will be immaterial to the P&L , though will result in slightly higher product revenue recognition.
Additionally, Pasek said that a year ago, he said revenue growth will be “low-single digit growth” (FY18-20) and now he is saying “mid-single digit growth,” driven by Flash, HCI, cloud data services.  Pasek said that in FY19 cloud data services will represents one point of growth.  (As an aside, we calculate FY19 cloud data services revenue, using the “one point of growth” metric at $60M, based on the latest quarter of total revenues, F3Q18 which was $1.52B, multiplied by 4, then multiplied by 1%).  So, cloud services revenue is expected to grow to FY19 of $60M and reach FY21 targets of $400-600M.  The company declined to state its FY18 cloud data services revenue when asked by the audience, so we take it that it is small.

The OCP Summit 2018 hit record attendance and we can can summarize the theme as that of continued disaggregation of network/server functions.  Examples of demonstrations, presentations and proposals associated with disaggregation are as follows: