Skip to content

Commit dba9638

Browse files
Merge pull request #267268 from joemarshallmsft/joe/nexus-sku
Operator Nexus SKUs reference
2 parents b9c1c5d + ef7921d commit dba9638

File tree

2 files changed

+35
-0
lines changed

2 files changed

+35
-0
lines changed

articles/operator-nexus/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -250,3 +250,5 @@
250250
href: reference-acl-configuration.md
251251
- name: Access Control List configuration examples
252252
href: reference-acl-examples.md
253+
- name: Operator Nexus Network Fabric SKUs
254+
href: reference-operator-nexus-fabric-skus.md
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
title: Azure Operator Nexus Fabric SKUs
3+
description: SKU options for Azure Operator Nexus Network Fabric
4+
ms.topic: article
5+
ms.date: 02/26/2024
6+
author: joemarshallmsft
7+
ms.author: joemarshall
8+
ms.service: azure-operator-nexus
9+
---
10+
11+
# Azure Operator Nexus Fabric SKUs
12+
13+
Operator Nexus Fabric SKUs for Azure Operator Nexus are meticulously designed to streamline the procurement and deployment processes, offering standardized bill of materials (BOM), topologies, wiring, and workflows. Microsoft crafts and prevalidates each SKU in collaboration with OEM vendors, ensuring seamless integration and optimal performance for operators.
14+
15+
Operator Nexus Fabric SKUs offer a comprehensive range of options, allowing operators to tailor their deployments according to their specific requirements. With prevalidated configurations and standardized BOMs, the procurement and deployment processes are streamlined, ensuring efficiency and performance across the board.
16+
17+
The following table outlines the various configurations of Operator Nexus Fabric SKUs, catering to different use-cases and functionalities required by operators.
18+
19+
| **S.No** | **Use-Case** | **Network Fabric SKU ID** | **Description** |
20+
|--|--|--|--|
21+
| 1 | Multi Rack Near-Edge | M4-A400-A100-C16-ab | <ul><li>Support 400-Gbps link between Operator Nexus fabric CEs and Provider Edge PEs</li><li>Support up to four compute rack deployment and aggregator rack</li><li>Each compute rack can have up to 16 compute servers</li><li>One Network Packet Broker</li></ul> |
22+
| 2 | Multi Rack Near-Edge | M8-A400-A100-C16-ab | <ul><li>Support 400-Gbps link between Operator Nexus fabric CEs and Provider Edge PEs </li><li>Support up to eight compute rack deployment and aggregator rack </li><li>Each compute rack can have up to 16 compute servers </li><li>One Network Packet Broker for deployment size between one and four compute racks. Two network packet brokers for deployment size of five to eight compute racks </li></ul> |
23+
| 3 | Multi Rack Near-Edge | M8-A100-A25-C16-aa | <ul><li>Support 100-Gbps link between Operator Nexus fabric CEs and Provider Edge PEs </li><li>Support up to eight compute rack deployment and aggregator rack </li><li>Each compute rack can have up to 16 compute servers </li><li>One Network Packet Broker for 1 to 4 rack compute rack deployment and two network packet brokers with deployment size of 5 to 8 compute racks </li></ul> |
24+
| 4 | Single Rack Near-Edge | S-A100-A25-C12-aa | <ul><li>Supports 100-Gbps link between Operator Nexus fabric CEs and Provider Edge PEs </li><li>Single rack with shared aggregator and compute rack </li><li>Each compute rack can have up to 12 compute servers </li><li>One Network Packet Broker </li></ul> |
25+
26+
The BOM for each SKU requires:
27+
28+
- A pair of Customer Edge (CE) devices
29+
- For the multi-rack SKUs, a pair of Top-of-Rack (TOR) switches per deployed rack
30+
- One management switch per deployed rack
31+
- One of more NPB devices (see table)
32+
- Terminal Server
33+
- Cable and optics

0 commit comments

Comments
 (0)