NUS Pricing

Nutanix Unified Storage PetaByte(PB) Club

Internal Sales and Commercials FAQ

 

Q1. What is Nutanix Unified Storage PB Club? 1

Q2. What is changing in the new pricing model? 1

Q3. What is the go live date? 2

Q4. What is the qualifying criteria for this pricing benefit? 2

Q5. How is the installed base calculated? 2

Q6. What will be the impact on mid term upgrades? 2

Q7. What will be the impact on renewals? 2

Q8. How is the pricing benefit applied? 3

Q9. What is the impact on in-progress quotes? 3

Q1. What is Nutanix Unified Storage PB Club?

A: For accounts with NUS install base >= 1000 TiB (Accounts with NUS installed capacity > 1000 TiBs) is considered while pricing, any expansion sale will be priced at the 1000 TiB+ tier, regardless of the expansion size.

 

NUS Install in the account Current pricing logic  New pricing logic
<1,000 TiB capacity tier is based on used capacity (TiB) in the quote Same as existing
>=1,000 TiB capacity tier is based on used capacity (TiB) in the quote Capacity tier is based on account-level installed base

 

Q2. What is changing in the new pricing model?

A: Accounts with an installed base greater than 1,000 TiB are eligible for pricing benefits.

Eg:

List Price table for NUS (pricebook v6, 3Yr price for production Support)

 

Case 1: Account A has installed capacity of 1200 TiBs, account is eligible for 1,000 TiB+ pricing. 

New quote for NUS PRO (650 TiB) for 3Yr Production Support

Quantity (a) Price per TiB (b) Total List price (c = a*b)
650 215 139,750

 

Case 2: Account B has an installed capacity of 650 TiBs, account is not eligible for 1,000 TiB pricing. 

New quote for NUS PRO (650 TiB) for 3Yr production Support

Quantity (a) Price per TiB (b) Total List price (c = a*b)
50 1470 73,500
150 945 141,750
450 336 151,200
Total Quantity = 650 366,450

Q3. What is the go live date? 

A: This new pricing benefit is live in production. 

Q4. What is the qualifying criteria for this pricing benefit?

A:  a) Account level installed base must exceed 1000 TiB . 

  1. b) Licenses in the installed base must not be expiring in the next 6 months. 
  2. c) Any new quotes  with capacity over 10,000 TiB will automatically receive the 1,000 TiB+ pricing benefit, regardless of the current installed base.

Q5. How is the installed base calculated?

A: Installed Base  = Sum of all active NUS licenses (STR + PRO) not expiring within 6 months.  Add on licenses are not counted towards installed capacity calculations.

 

Eg: An account has 600 TiB of NUS STR and 500 TiB of NUS PRO which are expiring after 1 year. The installed base for this account is 1100 TiB (500 +600) and thus it qualifies for 1,000 TiB + Pricing

Q6. What will be the impact on mid term upgrades?

A: Accounts with an installed base exceeding 1,000 TiB qualify for the pricing benefits during mid-term upgrade also, whether it is license and/or support upgrade.

Q7. What will be the impact on renewals? 

A: Renewal pricing remains unaffected; all existing rules and guidance continue to apply.

Q8. How is the pricing benefit applied?

A: When preparing quotes, Frontline automatically applies 1,000 TiB+ pricing for eligible accounts.

Q9. What is the impact on quotes in flight?

A: Approved Quotes: No change

Draft Quotes: Will be updated with new pricing if account is eligible

In Review quotes: Quotes in review will be reverted to Draft status and new pricing logic will be applied

Cloned or New quotes:  All cloned or new quotes automatically incorporate new pricing logic

Historic Guardrails

Product Object Field Value Guardrail Description
Nutanix Launchpad Promo Opportunity Type New Business Used with Account Type = Customer
Nutanix Launchpad Promo Opportunity Type Existing Business Used with Account Type = Ex – Customer
Nutanix Launchpad Promo Quoteline (NCI Promo SKUs) Quantity < = 192 Sum of all quantities of NCI Promo SKUs < = 192
Nutanix Launchpad Promo Quoteline (NCM Promo SKUs) Quantity < = 192 Quantity of NCM Promo SKU < = 192
Nutanix Launchpad Promo Quoteline Quantity > = 1 Min quantity of each quoteline >=1
Nutanix Launchpad Promo, Cloud Bundle 2.0 Quoteline Discount% < = Floor Discount on each quoteline cannot exceed Floor discount
Nutanix Launchpad Promo, Cloud Bundle 2.0 Quoteline Term > = 365 Min term of 12 months
Nutanix Launchpad Promo, Cloud Bundle 2.0 Quoteline Term < = 1825 Max term of 60 months
Nutanix Launchpad Promo Quote Erro Message The NCI/NCM Promo SKUs cannot be quoted above 192 cores. When Quantity <= 192 rule is violated.
EUC HS SKUs Opportunity Healthcare Workload EHR – EPIC – Hyperspace / Hyperdrive EHR – EPIC – Hyperspace / Hyperdrive AND
EUC HS SKUs Opportunity Region Americas USA Healthcare Americas USA Healthcare ( OR
EUC HS SKUs Opportunity Theater IN (EMEA, APAC) Either this or Americas USA Healthcare IN (EMEA, APAC) )
NX G9 NCI LoD Account Enable LOD for 2.0 TRUE Only flagged accounts eligible to quote the SKUs
NX G9 NCI LoD Quoteline Quantity = HW Core count Quantity must be equal to the HW core count for all G9 NCI LoD SKUs
NCI (Edge), NCI Quote Banner Message You are quoting NCI Edge feature add-ons as a standalone. Please confirm that the customer already has an NCI Edge Pro license. Message is displayed when feature add-on are quoted standalone
NCI (Edge), NCI Quote Feature Add-On When NCI Edge Pro or NCI Pro is selected Feature add-on (Security and Adv DR) is availalble to configure only when NCI Edge Pro or NCI Pro license tier is selected
NCI (Edge), NCI Quote Banner Message You are quoting NCI/NCI Edge product add-ons as a standalone. Please confirm that the customer already has an NCI/NCI Edge Pro or NCI/NCI Edge Ultimate license. Displayed when NDB add-on is quoted standalone
NCI (Edge) Quote Banner Message Please note restrictions for NCI Edge clusters – max 25 VMs allowed per cluster, and max 96 GB memory allowed per VM. Message is displayed when any NCI Edge SKUs are quoted
Cloud Bundles 2.0 Opportunity Theater EMEA Only quotable in EMEA theater
Cloud Bundles 2.0 Account Account Segment IN (Named Commercial, Named Public Sector, Territory, Channel Led) Guardrail to make the SKUs available to commercial segment only
Cloud Bundles 2.0 Opportunity Type New Business For new business accounts only
Cloud Bundles 2.0 Quoteline (NCI, NCM) Quantity < = 192 Bundle quantity <= 192, for both sales reps and sales ops
Cloud Bundles 2.0 Quoteline (NCI, NCM) Quantity > = 48 Bundle quantity >= 48, for both sales reps and sales ops
Cloud Bundles 2.0 Quoteline Discount% = 100% Sales Ops can quote 100% discount in case of RMA deals
Cloud Bundles 2.0 Opportunity DR status Approved A valid deal registration mandatory to quote the SKUs
Cloud Bundles 2.0 Quoteline (NUS) Quantity < = 10 NUS Promo capacity <= 10 TiB
Cloud Bundles 2.0 Quoteline (NUS) Quantity > = 5 NUS Promo capacity >= 10 TiB
NDL, NUS Quoteline Pricing Tiered Pricing is tiered, and not linear like other products
NDL Quoteline Quantity > = 25 Minimum quantity of 25 TiB, only for Sales Reps. Sales Ops can quote any quantity

SW Guardrail Common

Attribute Category Attribute Parameters Default Value Guardrail Description
Customers Type New / Existing Both
Term Min Term – Sales Reps Can select any term in months (from 1 to 84) 6 months Minimum term to be selected by Sales Reps
Term Max Term – Sales Reps Can select any term in months (from 1 to 84) 60 months Minimum term to be selected by Sales Reps
Term Min Term – Sales Ops Can select any term in months (from 1 to 84) 3 months Minimum term to be selected by Sales Ops
Term Max Term – Sales Ops Can select any term in months (from 1 to 84) 84 months Minimum term to be selected by Sales Ops
Quantity Quantity – Min Any number >=1 1
Quantity Quantity – Max Any number >=1 or blank blank
Message Banner Message Text Box to enter message to display on top of quotelines summary blank If (condition), then (message).
It is based on the conditions on the quote (for example, SKUs quoted or something in the quote)
Message Error Message Text Box to enter message to display when an error is met while quoting. blank If (condition), then (message).
Condition – when a quoting guardrails is violated.
Enable/Disable for other SKUs.
Quote Types Quote Types All quote types in Frontline, ability to deselect any one All
Discount Discount Cap – Max Target, Floor, Input (Fixed), None, <calculated expression> None Cannot discount above this threshold discount.
Example – It can be Floor of each Zone, or a fixed discount % for each zone.
Calculated Value – We should be able to use Good, Target, or Floor and create an expression. For example – (Floor +1)%
Pricing Price Curve Linear / Non-Linear Linear Simplify linear pricing, istead of using 0.3333 in the price curve file. Can we store 1 year number, and calculated other term rpcies.
Delayed Start Date Delayed Start Date – Active TRUE / FALSE TRUE Whether to allow or not allow delayed start date option to a product offering
+2 months option Plus Two Months Selection Yes / No Yes
Region Account Region 1 or more of the Account Regions All If the SKUs are to be quoted for specific account regions, add the region names.
For example, “Americas Enterprise North, Americas Enterprise East, Americas Enterprise West”
Account Segment Account Segment 1 or more of the Account Segments All
Hold the below for now
Dependency on another Product Allow Quoting – if another defined product has been booked Category of the independent product blank
Dependency on another Product Do Not Allow Quoting – if another defined product has been booked Category of the independent product blank

Guardrail of Frontline

Phase / Section / Heading Rule Number Frontline Rule Applicable Platforms Additional Information / Comments Ticket Number Date Added Date Modified
Historical Rules 1 Encrypted and Non-Encrypted Drives Mixing not allowed
To include NVMe SED also – post GA item in G9
All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 2 Total drive count should be within Min and Max drive slots available for the model depending on drive configuration
HDD + SSD, NVMe+SSD, All NVMe, NVMe Advanced, NVMe Advanced + NVMe

Mar 4 : G10 Drive configs: All NVMe & NVMe + SSD will be renamed to NVMe All Flash since there is no NVMe + SSD supported in G10

All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 3 HDD:SSD ratio >= 2:1 for models having Max drive slot > 4 (except 1175S) All G10 Platforms, All G9 Platforms, All G8 Platforms Override functionality available | CPQ-5559 NA (Carry forward)
Historical Rules 20 NX-3155G-G7 – For This model, GPU is not mandatory, means user should be able to add Model without adding any GPU
In G9, the platform name will be 3155
NX-3155G-G8, NX-3155-G9 BA-81824
NPI-764
Historical Rules 31 System flag = TRUE and Selected = FALSE then mark it as invalid option All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 32 External ID ends with model type string, then option is limited to that model type only (AF, HY, NVME)
Impact analysis for G9 to be done as G9 drive configurations are different. Details in BRD.
All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 33 Quote visibility controls availability of options based on logged in user’s role All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 34 CPU, RAM and Drive are mandatory for blocks
Feb 18: Exception to the above rule is the newly introduced compute only model type
All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 35 NIC ABL countries = Algeria, Afghanistan, Bangladesh, Brunei, Chad, Iraq, Kuwait, Lebanon, Libya, Malaysia, Mali, Pakistan, Qatar, Saudi Arabia, Yemen
Based on install country and shipping country and end customer country nics are removed based on the following matrix

Table link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=A2:A4

All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
NPI-383
NPI-47
Historical Rules 36 PSU – Based on Install Country, if install country is absent use Billing Country.

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B7:B11

Exception of U-PSU-2200-TR2.This rule should not apply to U-PSU-2200-TR2 from G8 onwards.
No geography based restrictions for any PSU SKUs apart from the ones mentioned in table

All G10 Platforms, All G9 Platforms, All G8 Platforms BA-81162
BA-8296
Historical Rules 37 `+2 months support is not allowed for quotes that is outside “Americas” region except “Brazil” – in other words +2 months should be available everywhere outside Americas and also in Brazil even if region is Americas All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 38 Appliance support is not allowed on NX Core quote All G8 Platforms NA (Carry forward)
Historical Rules 39 Hardware support is not allowed on NX Appliance quote All G8 Platforms NA (Carry forward)
Historical Rules 40 Max appliance support discount is 40% All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 41 Default Hardware support discount is 20% and max is 40% All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 42 Product options without category 1, category 2, category 3 and category 4 are removed All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 43 SED drives are not allowed if the install country belongs to any of the following countries *[“Cuba”, “Iran (Islamic Republic of)”, “Ukraine”, “Syrian Arab Republic”,* Armenia”, “Belarus”, “Kazakhstan”, “Kyrgyzstan”, “Russian Federation”]

CPQ-7062 – Countries names updated

All G10 Platforms, All G9 Platforms, All G8 Platforms CPQ-4095
CPQ-7062
Historical Rules 44 Federal support is not available outside “Americas USA Federal” sub theater on account All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 48 Mission Critical Support is based on the install address of the node All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 49 Discount on NRDK cannot exceed 40% All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 50 Sales rep cannot quote standalone NRDK All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 51 `+2 months support for NRDK is available opportunity region is “APAC” or “EMEA” or subRegion is “Americas Latin America All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 52 Nutanix Hardware Cannot be Quoted on HPE Quote All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 53 Upgrades/spares cannot be intermixed with other products on Brazil quote All G10 Platforms, All G9 Platforms, All G8 Platforms NA (Carry forward)
Historical Rules 54 TPM is not supported for the following countries [“Cuba”, “Iran (Islamic Republic of)”, “Ukraine”, “Armenia”, “Belarus”, “Kazakhstan”,
“Kyrgyzstan”, “Russian Federation”, “Syrian Arab Republic”]

CPQ-7062- Countries names updated

All G10 Platforms, All G9 Platforms, All G8 Platforms CPQ-4095
CPQ-7062
Historical Rules 55 Ultimate license or encryption add-on is required for adding SED drives

For new portfolio quote:
Ultimate license (NCI/NCI-D/EUC ULT) or security addon (NCI/NCI-D/NUS Security) is required for adding SED drives

Needs to apply for NVMe SED also in future (post GA item for G9)

14-Jul-2025 update (change with AOS 7.3)-
Ultimate license or Pro license or NUS-Starter+Security Add-On is required for adding SED drives

For new portfolio quote:
Ultimate license (NCI/NCI-D/EUC/NKP-FS/NCI-E/NAI-GPT) or Pro license (NCI/NCI-D/EUC/NKP-FS/NCI-E/NUS-Pro/NAI-GPT) or NUS Starter (NUS-STR) with security add-on (NUS) is required for adding SED drives

Needs to apply for NVMe/SSD/HDD SEDs also

The additional security add-on is only required for NUS Starter. It is not required for the mentioned Ultimate or Pro licenses

All G10 Platforms, All G9 Platforms, All G8 Platforms Override functionality required (WIP – NPI-810)
Has to be applied to (SSE, HDE both and NVMe SED for post GA in G9)
NA (Carry forward)
NPI-436
NPI-1573
7/24/2025
Historical Rules 57 Operating Temperature rules for G8 Platforms. Need to display operating temperature message, based on TDP values as per below table.

The configuration should be quotable but the warning message must be displayed.

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B14:B18

All G8 Platforms, NX-3060-G8, NX-1065-G8, NX-8035-G8 BA-81162
Historical Rules 58 Operating Temperature rules for G8 Platforms. Need to display operating temperature message, based on TDP values as per below table.

The configuration should be quotable but the warning message must be displayed.

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B21

All G8 Platforms, NX-8155-G8 BA-81823
Historical Rules 59 Memory + Processor constraints for G8 Platforms. Need to display below message, based on TDP values as per below table and also block the config.
The configuration should NOT be quotable and the error message must be displayed.

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B24

All G8 Platforms, NX-8170-G8 BA-81823
Historical Rules 60 Memory + Processor constraints for G8 Platforms. Need to display below message, based on TDP values as per below table and also block the config.
The configuration should NOT be quotable and the error message must be displayed.

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B27

All G8 Platforms, NX-3170-G8 BA-81824
Historical Rules 61 GPU & NIC related option constraints for Platform NX-3155G-G8.
Please note that these rules should apply only to Nvidia T4 GPU (C-GPU-T4-16GB). There will be separate rules for different GPU models (Post GA)

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B30:B32

NX-3155G-G8 BA-81824
Historical Rules 62 CPU + Memory constraints for G8 Platforms.
The configuration should NOT be quotable and the error message must be displayed.

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B35

All G8 Platforms, NX-3060-G8 BA-81162
Historical Rules 66 Existing Portfolio:
The configuration should NOT be quotable and the error message must be displayed.
(Config and error message in the table link below under “Existing Portfolio” rows)

New Portfolio:
The configuration SHOULD BE quotable and the warning message must be displayed.
(Config and error message in the table link below under “New Portfolio” rows)

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B39:B42

All G10 Platforms, All G9 Platforms, All G8 Platforms Override functionality available | CPQ-5559 BA-81824
NPI-436
Historical Rules 67 The configuration should NOT be quotable and the error message must be displayed

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B45:B46

All G10 Platforms, All G9 Platforms, All G8 Platforms Override functionality available | CPQ-5559 BA-81824
NPI-436
NPI-1015
Historical Rules 70 Operating Temperature rules for G8 Platforms. Need to display operating temperature message, based on TDP values as per below table.

The configuration should be quotable but the warning message must be displayed.

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B49

All G8 Platforms, NX-8150-G8 NPI-214
Historical Rules 71 GPU-related option constraint (3155G)
The configuration should be quotable but the warning message must be displayed.

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B52

NX-3155G-G8 NPI-333
NPI-349
Historical Rules 72 GPU & NIC-related option constraints for Platform NX-3155G-G8.

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B55:B56

GPU impacted – All GPUs starting with “C-GPU-A”, L40S (C-GPU-L40S-48GB,C-GPU-L40S-48GB-CM )

GPU Quantity Selected – NIC Quantity Supported – Message
* 1x GPU – 1x, 2x, 3x NICs –
* 2x GPU – 1x, 2x NICs – Maximum 2 NICs supported with 2 quantity of <GPU Name>

NX-3155G-G8 NPI-238
NPI-349
NPI-946
Historical Rules 74 GPU & NIC related option constraints for Platform NX-3155G-G8.
Please note that these rules should apply only to Nvidia A2 GPU (C-GPU-A2-16GB)

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B59:B61

GPU Quantity Selected – NIC Quantity Supported – Message
* 1x GPU – 1x, 2x, 3x NICs –
* 2x, 3x, or 4x GPU – 1x , 2x NICs – Maximum 2 NICs supported with 2, 3 or 4 quantity of NVIDIA A2 GPU (16GB)
* 5x GPU – 1x NICs – Only 1 NIC supported with 5 quantity of Nvidia A2 GPU (16GB)

NX-3155G-G8 NPI-427
Historical Rules 75 GPU-related option constraint for Platform NX-3155G-G8.

Please note: If GPU with SKU: C-GPU-A2-16GB is selected Rule 71 and 72 should not trigger.

NX-3155G-G8 NPI-427
Historical Rules 76 GPU-related option constraint for Platform NX-3155GN-G8.

This rule applies to T4 and A2 GPUs only

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B64:B66

NX-3155GN-G8 NPI-510
NPI-591
Historical Rules 77 Platform: 3155GN-G8 | This rule applies only to A series GPUs (except A2)

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B69:B70

Rules 71 and 73 also apply to all A series GPUs (except A2)

NX-3155GN-G8 NPI-510
Historical Rules 82 GPU & Country related constraints

Table Link – https://docs.google.com/spreadsheets/d/1qRbFqpCxwChvrei39URlF9Bce6cKmLIYLHi9_PQTzdY/edit?gid=1085857383#gid=1085857383&range=B73

Also refer to changes via BA-103927

All G10 Platforms, All G8 Platforms NPI-673 (Demand shaping)
BA-103927
Historical Rules 83 NVMe + SSD mixing restrictions:

Only configurations with equal NVMe SSD & SATA/SAS SSD capacities are to be supported.

Applicable to all HW quotes, irrespective of the Software (HCI / NCI / NUS / Files etc.. ) selected.

Example:
Supported: Combination of 7.68TB NVMe with 7.68 SATA/SAS SSD is supported
Not Supported: Combination of 1.92TB NVMe with 7.68 SATA/SAS SSD is not supported

All G10 Platforms, All G9 Platforms, All G8 Platforms Override functionality for exception | NPI-770 NPI-713
Historical Rules 84 PSU to CPU mapping defined in G8 for 3060-G8 All G8 Platforms PSU is not a C-SKU in G9 BA-80037
Historical Rules 85 PSU to Power cord mapping defined in G8 for 3060-G8 All G8 Platforms PSU is not a C-SKU in G9 BA-80037
Historical Rules 86 Power cord to Country mapping defined in G8 including RoW countries

Link – https://docs.google.com/document/d/14mW2E3ejnARb1CRAOQ8Aha8TuBAY-RXWWU_bVVuLEHI/edit?tab=t.0

All G10 Platforms, All G9 Platforms, All G8 Platforms BA-80037,
NPI-317
Historical Rules 87 NG8 NIC intermixing rules defined as part of NG8: BRD (Phase 1 & Phase 2) All G8 Platforms Phase 1 & 2 are irrelevant for G9 as C-LOM is an option for G9 NPI-506, NPI-510
Historical Rules 88 NG8 BRD – Phase 3 – Req. 9 – Intermixing rules for LOM-NIC (#1)
Big Twins when LOM is NONE
Same rules as in Phase 1 with one exception below
C-NIC-10G2D1BT not a valid option for AOC 1, 2, 3 (should not show up in dropdown)
Big Twins when LOM is “C-LOM-10G2D1BT” (CM & non-CM SKUs):
C-NIC-10GBT2-A and C-NIC-10GBT2-A-Q are not valid options for AOC 1, 2, 3 (should not show up in dropdown)
All G8 Platforms Rule irrelevant for G9 as C-LOM-NONE is not an option for G9 NPI-540
Historical Rules 89 NG8 BRD – Phase 3 – Req. 9 – Intermixing rules for LOM-NIC (#2)
Big Twins when LOM is “C-LOM-10G2D1BT” (CM & non-CM SKUs):
C-NIC-10GBT2-A and C-NIC-10GBT2-A-Q are not valid options for AOC 1, 2, 3 (should not show up in dropdown)
All G9 Platforms, All G8 Platforms Rule to be extended to ALL G9 platforms NPI-540
Historical Rules 90 NG8 BRD – Phase 3 – Req. 8, 10, 11 All G8 Platforms C-LOM is an option in G9 – but other messaging related changes not required in G9 NPI-540
Historical Rules 91 NG8 Big Twins when LOM is “C-LOM-10G2B1BT” (CM & non-CM SKUs):
C-NIC-10G2D1BT is not a valid option for Add-on card NIC (Networking section in FL – should not show in the dropdown for the aforementioned LOM) – BRD
All G9 Platforms, All G8 Platforms Rule to be extended to ALL G9 platforms NPI-766
NPI-992
NPI-993
Historical Rules 92 AOS 6.5.1 Capacity rules – BRD All G9 Platforms, All G8 Platforms Override functionality for min capacity and partial pop rules NPI-735
Historical Rules 93 NIC Card: C-NIC-25G4E1/-CM SKU should NOT be quotable in non-ALB countries for G8 platforms. NIC Country of Origin: Non-Israel.

In G9 platforms – the SKU should follow generic rules and be quotable in ALL countries (no guardrails) as COO is non-Israel

All G8 Platforms G8 RULE ONLY CPQ-9240
Historical Rules 94 8155:
For “NOT No snapshot” (i.e. RPO-1 Hr or RPO-6Hr) OR Files Dedicated OR Objects Dedicated OR NUS Dedicated chosen
For 8 TB HDD capacity, <SSD or NVMe> with a capacity greater than 1.92 TB <SSD or NVMe> required on 8155 partially configured node.

Message: “For 8 TB HDD capacity, 1.92 TB<SSD or NVMe> capacity is allowed on 8155 partially configured node only with no snapshots.”

If “No snapshot” is chosen – this rule should not apply.

Note: Messaging should say NVMe or SSD based on drive selected as G9 will have NVMe+HDD as Hybrid configuration for 8155
NOTE: The rule should apply to HDEs, SSEs (NVMe SED for G9) too.

27Mar2025: NOTE: The rule should apply to HDEs, SSEs (NVMe SED for G9) & NVE too.

All G9 Platforms, All G8 Platforms, All G10 Platforms Override functionality available| NPI-735 NPI-735
Historical Rules 95 8155:
For “NOT No snapshot” (i.e. RPO-1 Hr or RPO-6Hr)
For 12 TB HDD capacity, <SSD or NVMe> with a capacity greater than 1.92 TB 3.84 <SSD or NVMe> required on 8155 partially configured node.

Message: “For 12 TB HDD capacity, <SSD or NVMe> with a capacity greater than 3.84 TB <SSD or NVMe> required on 8155 partially configured node with snapshots.”

If “No snapshot” is chosen OR Files Dedicated OR Objects Dedicated OR NUS Dedicated
For 12 TB HDD capacity, <SSD or NVMe> with a capacity greater than 1.92 TB <SSD or NVMe> required on 8155 partially configured node.

Message: “For 12 TB HDD capacity, <SSD or NVMe> with a capacity greater than 1.92 TB <SSD or NVMe> required on 8155 partially configured node.”

Note: Messaging should say NVMe or SSD based on drive selected as G9 will have NVMe+HDD as Hybrid configuration for 8155.

NOTE: The rule should apply to HDEs, SSEs (NVMe SED for G9) too.

27Mar2025: NOTE: The rule should apply to HDEs, SSEs (NVMe SED for G9) & NVE too.

All G9 Platforms, All G8 Platforms, All G10 Platforms Override functionality available| NPI-735 NPI-735
Historical Rules 96 For Hybrid configurations (HDD + SSD / HDD +NVMe)

If “No snapshot” replication requirement
-If node capacity <=136TB, SSD (NVMe for G9) capacity should be a minimum of 4% of Total capacity
-If node capacity > 136 TB, SSD (NVMe for G9) capacity should be a minimum of 10% of Total capacity

If NOT “No snapshot” replication requirement
-If node capacity <=60 TB, SSD (NVMe for G9) capacity should be a minimum of 4% of Total capacity
-If node capacity > 60 TB, SSD (NVMe for G9) capacity should be a minimum of 10% of Total capacity

If NUS Dedicated OR Objects Dedicated OR Files Dedicated OR HW only quote with Dedicated NUS chosen: SSD (NVMe for G9) capacity should be a minimum of 6% of Total capacity

Exceptions to the rule:
8155: Below configurations should be allowed in FL as exceptions:
10*6TB HDD / HDE + 2*1.92TB SSD / SSE (NVMe for G9)
10*8TB HDD / HDE + 2*3.84TB SSD / SSE (NVMe for G9)

8155: Below configurations should be allowed in FL as exceptions with “No Snapshot” ONLY:
8*18TB HDD / HDE+ 2*7.68TB SSD / SSE (NVMe for G9)
10*18TB HDD / HDE + 2*7.68TB SSD / SSE (NVMe for G9)

NOTE: The rule should apply to HDEs, SSEs (NVMe SED for G9) too.

27Mar2025: The following Exceptions have been added
3155: Below configuration should be allowed in FL as exceptions:
4*18TB HDD + 2*3.84TB NVMe

3035: Below configuration should be allowed in FL as exceptions:
4*18TB HDD + 2*3.84TB SSD / NVME
NOTE: The rule should apply to HDEs, SSEs, NVEs too.

All G9 Platforms, All G8 Platforms, All G10 Platforms Override functionality available| NPI-735 NPI-735
Historical Rules 97 For “NOT No Snapshot” (i.e. RPO-1 Hr, RPO-6 Hr)
8155: 18 TB HDD capacity is not supported.
Message: “18 TB HDD capacity is not supported on 8155 with snapshots.”

For “No snapshot” OR Files Dedicated OR Objects Dedicated OR NUS Dedicated
For 18 TB HDD capacity, SSD (NVMe for G9) with a capacity greater than 3.84 TB SSD (NVMe for G9) required on 8155 partially configured node.
Message same as rule.

Note: Messaging should say NVMe or SSD based on drive selected as G9 will have NVMe+HDD as Hybrid configuration for 8155

NOTE: The rule should apply to HDEs, SSEs too.

27Mar2025: NOTE: The rule should apply to HDEs, SSEs (NVMe SED for G9) & NVE too.

All G9 Platforms, All G8 Platforms, All G10 Platforms Override functionality available| NPI-735 NPI-735
Historical Rules 98 When the CPU which is not Energy Star compliant for a particular platform is selected then fire the below warning message
“Please note <CPU name> is excluded from Energy Star certification for <Platform Name>”
All G10 Platforms, All G9 Platforms Applicable for NX-G9 for now and will extend to NX-G8 also in future NPI-900
NPI-1015
NPI-1439
Historical Rules 99 Below message should fire in Frontline UI Summary page:
TPM 2.0 is offered as a security hardware option with <platform name>. Please be sure to evaluate the customer’s security requirements and add to the configuration as necessary.
All G10 Platforms, All G9 Platforms Applicable for NX-G9 for now and will extend to NX-G8 also in future NPI-894
NPI-1439
Historical Rules 100 Below messages should be present in Quote Document based in whether TPM is selected or not selected in the configuration that is quoted:

With TPM:
This <platform name> configuration quote includes the TPM 2.0, a security hardware, which may be leveraged to support a security feature. Kindly verify this configuration aligns with your security plan.

Without TPM:
This <platform name> configuration quote does not include the TPM 2.0, a security hardware, which may be leveraged to support a security feature. Kindly verify this configuration aligns with your security plan.

All G10 Platforms, All G9 Platforms Applicable for NX-G9 for now and will extend to NX-G8 also in future NPI-894
NPI-1439
G9 Phase 1 | Section 1 : New G9 Rules 1 NX Appliance is not supported on G9 platforms. If an Appliance quote hits Frontline through another system /API – system should block that quote and throw error message:
If G8 systems are still quotable: “NX Appliance quote type is not supported for G9 platforms. Please quote G9 platforms as NX Core. Alternatively, you can quote G8 platforms as NX Appliance”
If G8 systems are not quotable (Inactive): ““NX Appliance quote type is not supported for G9 platforms. Please quote G9 platforms as NX Core.”
All G8 Platforms, All G9 Platforms NPI-761
G9 Phase 2 | Section 2: New G9 Rules 1 As specified in G9 BRD: HBA is a new selectable component in the workflow for NX-8155-G9, NX-8170-G9, NX-3155-G9, NX-8155A-G9, NX-1175S-G9 (All G9 platforms except 1065-G9,3060-G9,3035-G9,8150-G9).

The HBA component visibility is dependent on drive selected.

HBA should be selectable if one of the drives is either HDD or SSD (incl. encrypted parts). HBA should NOT be selectable for All NVMe / All NVMe SED drive configuration.

All G9 Platforms NPI-762
NPI-764
G9 Phase 2 | Section 2: New G9 Rules 2 For NX-8170-G9, 100GbE NIC should not be allowed with 128GB Memory option.
Message: “100GbE NIC is not allowed with 128 GB Memory for NX-8170-G9.”
NX-8170-G9 Override functionality Required NPI-762
NPI-1411
G9 Phase 2 | Section 2: New G9 Rules 3 For NX-8170-G9, If HBA is available and selected for the chosen drive configuration: Quantity option available for all AOC NIC reduces by 1, except 100GbE NIC

Error message:: “Please note for All SSD drive configuration, you can select a maximum of 2 NIC cards. Switch over to All NVMe, if you want 3 NIC cards in your system.”

Example: If HBA NOT selected C-NIC-25G2D1 will have quantity options as 1,2 and 3 per product options available C-NIC-100G2E1 will have quantity options as 1,2 per product options available

If HBA selected C-NIC-25G2D1 will have quantity options as 1,2 (1 less per product options available) C-NIC-100G2E1 will have quantity options as 1,2 per product options available

21-Jan-25: FYI, NIC is not a mandatory component for NX-8170-G9

NX-8170-G9 NPI-762
G9 Phase 2 | Section 2: New G9 Rules 4 8155-G9 and 8155A-G9
On a partially configured node, for hybrid configurations with a replication requirement (i.e. RPO-1Hr, RPO-6Hr):
15.36 TB NVMe/ SSD should not be allowed with HDD capacity >=12 TB
Message: “For <xx TB <HDD/HDE> capacity, 15.36 TB<SSD or NVMe> capacity is allowed on <8155/8155A> partially configured node only with no snapshots.”

The rule should also apply to SSE and NVMe SED (post-GA).

NX-8155-G9, NX-8155A-G9 Override functionality Required NPI-762
G9 Phase 2 | Section 2: New G9 Rules 5 8155 specific rules in NPI-735 under Section 5.2 and Section 5.3 should extend to 8155A-G9 as well – BRD
This extends to the warning/error messages i.e. whenever a rule gets triggered for 8155A – the messaging should say 8155A and not 8155.
NX-8155-G9, NX-8155A-G9 Override functionality required NPI-762
G9 Phase 3 | Section 3: New G9 rules 1 GPU & NIC related option constraints for Platform NX-3155-G9.
Please note that these rules should apply only to Nvidia T4 (C-GPU-T4-16GB), A2 (C-GPU-A2-16GB) and Nvidia L4 (C-GPU-L4-24GB) GPUs for Hybrid / All SSD configuration

Table Link

NX-3155-G9 NPI-764
NPI-942
G9 Phase 3 | Section 3: New G9 rules 2 GPU & NIC-related option constraints for Platform NX-3155-G9 | This rule applies only to A series GPUs (except A2), Nvidia L40s GPU, Nvidia L40, Nvidia H100, Nvidia H100-NVL GPU for Hybrid / All SSD configuration

Table Link

*Nvidia L40s GPU, Nvidia L40, Nvidia H100, Nvidia H100-NVL GPU for Hybrid / All SSD configuration are part of the above rule & not the except list

NX-3155-G9
G9 Phase 3 | Section 3: New G9 rules 3 GPU & NIC related option constraints for Platform NX-1175S-G9.

Table Link

NX-1175S-G9
G9 Phase 3 | Section 3: New G9 rules 4 For 1175S Hybrid configuration (NVMe + HDD) | This rule applies for RPO-1Hr, RPO-6Hr and No Snapshot RPO 24-Hr
If nodes are configured with 2 NVMe + 2 HDDs configuration, the NVMe capacity should be a minimum of 30 % or more of the overall node capacity.”
When this percentage is calculated round up the percentage to the whole number
NX-1175S-G9 Override functionality Required NPI-764
G9 Phase 3 | Section 3: New G9 rules 5 For 1175S-G9: If All Flash drive configuration is chosen then minimum 4 quantity of 32GB memory must be selected NX-1175S-G9 NPI-764
NPI-1015
G9 Phase 3 | Section 3: New G9 rules 6 For 1175S-G9: When C-CPU-5415+ is selected below message should fire
“Please note 5415+ CPU is excluded from Energy Star certification”
NX-1175S-G9 NPI-764
G9 Phase 3 | Section 3: New G9 rules 7 When the CPU which is not Energy Star compliant for a particular platform is selected then fire the below warning message
“Please note <CPU name> is excluded from Energy Star certification for <Platform Name>”
All G9 Platforms, All G8 Platforms Applicable for NX-G9 for now and will extend to NX-G8 also in future NPI-900
NPI-1015
G9 Phase 3 | Section 3: New G9 rules 8 Below message to be displayed in the Frontline choose Hardware specification page beside “+ Add TPM”
“TPM is optional and is not selected by default. Please select based on the customer’s security requirement.””
All G9 Platforms, All G8 Platforms Applicable for NX-G9 for now and will extend to NX-G8 also in future NPI-894
G9 Phase 3 | Section 3: New G9 rules 9 Below message should fire in Frontline UI Summary page:

TPM 2.0 is offered as a security hardware option with <platform name>. Please be sure to evaluate the customer’s security requirements and add to the configuration as necessary.

All G9 Platforms, All G8 Platforms Applicable for NX-G9 for now and will extend to NX-G8 also in future NPI-894
G9 Phase 3 | Section 3: New G9 rules 10 Below messages should be present in Quote Document based in whether TPM is selected or not selected in the configuration that is quoted:

With TPM:
This <platform name> configuration quote includes the TPM 2.0, a security hardware, which may be leveraged to support a security feature. Kindly verify this configuration aligns with your security plan.

Without TPM:
This <platform name> configuration quote does not include the TPM 2.0, a security hardware, which may be leveraged to support a security feature. Kindly verify this configuration aligns with your security plan.

All G9 Platforms, All G8 Platforms Applicable for NX-G9 for now and will extend to NX-G8 also in future NPI-894
G9 Phase 3 | Section 3: New G9 rules 11 In 8155-G9 and 8155A-G9 for Hybrid Configuration (HDD + SSD/ HDD + NVMe)

24TB HDD should be available for selection only if NUS Dedicated Cluster/ Files and Objects Dedicated Cluster is selected. It should not be available for selection if NCI Cluster/AOS Cluster is selected.

For NUS Dedicated Cluster/ Files and Objects Dedicated Cluster:

Quantity 2 of 3.84TB SSD/NVMe should not be allowed for selection with 24TB HDD and below error should fire:

“Select quantity 4 of 3.84TB SSD/NVMe. If quantity 2 SSD/NVMe is desired then select capacity >= 7.68TB SSD/NVMe”

NX-8155-G9 NPI-940
G9 Phase 3 | Section 3: New G9 rules 12 GPU & NIC related option constraints for Platform NX-3155-G9.
Please note that these rules should apply only to Nvidia T4 (C-GPU-T4-16GB), A2 (C-GPU-A2-16GB) and Nvidia L4 (C-GPU-L4-24GB) GPUs for All NVMe configuration

Table Link

NX-3155-G9 NPI-942
G9 Phase 3 | Section 3: New G9 rules 13 GPU & NIC related option constraints for Platform NX-8155A-G9 with All NVMe configuration (No HBA).

Table Link

NX-8155A-G9 NPI-1107
G9 Phase 3 | Section 3: New G9 rules 14 GPU & NIC-related option constraints for Platform NX-3155-G9 | This rule applies only to A series GPUs (except A2), Nvidia L40s GPU, Nvidia L40, Nvidia H100, H100-NVL GPU for All NVMe configuration

Table Link

NX-3155-G9 NPI-946
NPI-945
NPI-944
NPI-1302
G9 Phase 3 | Section 3: New G9 rules 15 GPU & NIC-related option constraints for Platform NX-8155A-G9 | This rule applies to NVIDIA L4, NVIDIA A16 GPUs under All Nvme & Nvme + SSD (and all configs that allow for NIC & GPU selection)

Table Link

NX-8155A-G9 NPI-946
NPI-945
NPI-944
NPI-1302
G9 Phase 3 | Section 3: New G9 rules 16 Introduce new PCIe Gen 5 – PM9D3a SKUs -C-NVM-3.84TB-AB-A, C-NVM-7.68TB-AB-A & C-NVM-15.36TB-AB-A.
These drives will be supported:
1. For EMR CPUs only under platforms 8170-G9, 8150-G9, 8155-G9, 3155-G9
2. For SPR & EMR under platform 1175S-G9
3. For SPR & EMR under platform 1150S-G9
4. For AMD under platform 8155A-G9

Error message to be shown if a user selects an SPR CPU with these SKUs for 8170,8150,8155,3155 platforms:
“PCIe Gen5 NVMe drive is not offered with ‘Sapphire Rapids’ processor for NX-8170-G9, NX-8150-G9, NX-8155-G9, NX-3155-G9”

NX-8170-G9, NX-8150-G9, NX-8155-G9, NX-3155-G9, NX-1175S-G9, NX-1150-G9, NX-8155A-G9 NPI-1351
G9 Phase 3 | Section 3: New G9 rules 17 With NPI-1410, new NVME SED SKUs are being introduced.
List of SKUs – C-NVE-3.84TB-A, C-NVE-7.68TB-A, C-NVE-15.36TB-A
NVME SED Rules
1. Intermixing Rules
1.1 Model Types leveraged
1.1.1 All NVMe & NVMe + SSD – for NVMe SEDs
1.1.2 Hybrid – for (NVMe SED + HDD SED)
1.2 Mixing (NVMe SED + NVMe) is not supported
1.3 Mixing (NVMe SED + HDD) is not supported
1.4 NVMe SED + SSD SED is not supported
2. The drives will be supported for
2.1 Only EMR CPUs for platforms NX-3155-G9, NX-8150-G9, NX-8155-G9, NX-8170-G9
2.2 Both SPR and EMR CPUs for NX-1175S-G9, NX-1150S-G9
3. AOS 7.3 BRD Rules Apply

Apr 30: “NVMe SEDs are not supported with “Sapphire Rapids” processors for NX-3155-G9, NX-8150-G9, NX-8155-G9, NX-8170-G9”

25 June 25: Whenever NVMe SEDs are selected, a message to be displayed “AOS 7.3 (or higher) is required for NVMe SED support”

NX-8170-G9, NX-8150-G9, NX-8155-G9, NX-3155-G9, NX-1175S-G9, NX-1150-G9 NPI-1410 25-June-2025
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 1 If any of the 32GB, 64GB, 96GB DDR5-5600 DIMM is selected with Sapphire Rapids processor, then below error should fire:

“If the user wants DDR5-5600 memory, then select the Intel 5th Generation ‘Emerald Rapids’ processor.”

“DDR5-5600 memory is not supported with ‘Sapphire Rapids’ processor. Select the Intel 5th Generation ‘Emerald Rapids’ processor instead”

Above rule is not applicable to NX-1150S-G9 platform & AMD platform 8155A-G9 (added AMD platform on June 25)

Enable to 32Gb and 64GB DDR5-5600 for all SPR SKU

The above message will need to be modified and restricted to only when 96GB DDR5-5600 DIMM is selected with Sapphire Rapids processor,
“96 GB DDR5-5600 memory is not supported with ‘Sapphire Rapids’ processor. Select the Intel 5th Generation ‘Emerald Rapids’ processor instead”

Above rule is applicable for 1150s-G9.
FYI – 128GB DDR5-4800 is supported with EMR, no changes there.

All G9 Platforms NPI-1015
NPI-1208
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 2 Below pop up message should fire only if NX-8155-G9, NX-8155A-G9 and NX-3155-G9 platforms are quoted. The message should pop up as soon as the platform is selected while in the configuration page:
“Default rails kits for NX-3155-G9, NX-8155-G9 and NX-8155A-G9 platforms have a longer nominal length as compared to other G9 platforms. For more information, please refer to this documentation. If a shorter rail kit is preferred then please select U-RAIL-1U-D.”

Below pop up message should fire only if NX-8155-G9, NX-8155A-G9 and NX-3155-G9 platforms are quoted. The message should pop up as soon as the platform is selected while in the configuration page:
“Default rails kits for NX-3155-G9, NX-8155-G9 and NX-8155A-G9 platforms have a longer nominal length as compared to other G9 platforms. For more information, please refer to this documentation. If a shorter rail kit is preferred then please select U-RAIL-1U-D.”

11Mar2025: The link is updated in the above change

NX-8155-G9, NX-8155A-G9, NX-3155-G9 Applicable to NX-8155-G9, NX-8155A-G9 and NX-3155-G9 platforms NPI-1142
BA-108568
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 3 Below pop up message should fire only if NX-9151-G9 platform is quoted. The message should pop up as soon as the platform is selected while in the configuration page:
“The chassis depth of the NX-9151-G9 platform is 900mm (35.4 inch). It is advised to use a rack with 1200mm depth.For more information, please refer to this documentation.”
“The NX-9151-G9 chassis depth is 900 mm (35.4 in.). Mount the chassis in a rack with a minimum depth of 1200 mm (47.24 in.). For more information, please refer to this documentation.”

“The NX-9151-G9 chassis depth is 900 mm (35.4 in.). Mount the chassis in a rack with a minimum depth of 1200 mm (47.24 in.). For more information, please refer to this documentation.”

11Jun2025: Link further updated to exact section
12Mar2025: The link is updated in the above change

NX-9151-G9 Applicable to NX-9151-G9 platform NPI-1142
BA-108568
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 4 If Emerald Rapids processor is selected then below mentioned GPUs should not be available for selection in the GPU dropdown.
C-GPU-T4-16GB
C-GPU-T4-16GB-CM
C-GPU-A2-16GB
C-GPU-A2-16GB-CM
C-GPU-A40-48GB-A
C-GPU-A40-48GB-A-CM
All G9 Platforms NPI-1015
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 5 Disable 32GB or 64GB DDR5-4800 with EMR processors only 128GB DDR5-4800 is supported with EMR
Remove the 32Gb and 64GB DDR5-4800 for all SPR SKU –
*Exception of 64GB to be allowed with 9151-G9 platform & both 32 & 64 GB to be allowed with 8155A-G9
*Exception 128GB DDR5-4800 is not supported with NX-9151-G9 EMR
All G9 Platforms NPI-1208
NPI-1409
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 6 When the CPU which is not Energy Star compliant for a particular platform is selected then fire the below warning message
“Please note <CPU name> is excluded from Energy Star certification for <Platform Name>”
For NX-1150S G9, the following CPUs are not Energy Star Compliant C-CPU-3408U and C-CPU-4509Y
All G9 Platforms, All G8 Platforms NPI-1054
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 7 GPU & NIC-related option constraints for Platform NX-1150S-G9 for All NVMe configuration

Table Link

NX-1150-G9 NPI-1054
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 8 NX-9151-G9 (MGX Phase 2) – Rules on NIC & GPU
C-NIC-200G2A1 & C-NIC-200G2A1-Q – Mellanox CX7 : will be supported only with EMR processors
C-GPU-H100-NVL – will be supported only with EMR processors

C-NIC-100G2A2 & C-NIC-100G2A2-Q- is supported only with SPR processors
C-GPU-L40S-48GB-B – is supported only with SPR processors

30Jan25 – C-GPU-L40S-48GB-B is supported with both SPR and EMR processors
27Oct25 – C-NIC-100G2A2 & C-NIC-100G2A2-Q is supported with both SPR and EMR Processors

NX-9151-G9 NPI-1298
NPI-1350
NPI-1707
27-Oct-2025
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 9 C-MEM-64GB-5600-S on NX-9151-G9 MGX
C-MEM-64GB-5600-S and C-MEM-64GB-5600-S-CM will only be supported by EMR processors for NX-9151-G9.

C-MEM-128GB-4800 on NX-9151-G9 MGX
C-MEM-128GB-4800 and C-MEM-128GB-4800-CM will only be supported by SPR processors for NX-9151-G9.

NX-9151-G9 NPI-1409
G9 Phase 5 | Section 4: G9 Compute-Only Configurations 1 HBA is not a valid component in zero-drive compute-only configuration. HBA should not appear as a selectable component when compute only model type is selected for these platforms All G9 Platforms NPI-1210
NPI-1349
G9 Phase 5 | Section 4: G9 Compute-Only Configurations 2 NIC-GPU rules for NX-8170-G9 , NX-8155-G9 , NX-1175S-G9 Compute-Only Model Type are as follows –

Table Link

**Note – 3 NICs are not supported when 100GbE NIC is selected with NX-8170-G9 (Refer: G9 Phase 2 | Section 2: New G9 rules)

NX-8155-G9, NX-8170-G9, NX-1175S-G9 NPI-1349
G10 Phase 1: G10 Rules 1 As specified in G10 BRD:
HBA is a selectable component in the workflow for NX-8170-G10

The HBA component visibility is dependent on the drive selected.

HBA should be selectable if one of the drives is either HDD or SSD (incl. encrypted parts). HBA should NOT be selectable for All NVMe / All NVMe SED drive configuration.

NX-8170-G10 NPI-1408 10-Mar-2025
G10 Phase 1: G10 Rules 2 For NX-8170-G10, 100GbE and 200GbE NIC should not be allowed with 128GB Memory option.
Message: “100GbE and 200GbE NIC is not allowed with 128 GB Memory for NX-8170-G10.”
NX-8170-G10 To have override functionality NPI-1408 26-Mar-2025 29-May-2025
G10 Phase 1: G10 Rules 5 Ultimate license or encryption add-on is required for adding SED drives
For new portfolio quote:
Ultimate license (NCI/NCI-D/EUC ULT) or security addon (NCI/NCI-D/NUS Security) is required for adding SED drives
Needs to apply for NVMe SED also in future
All G10 Platforms NPI-1408 10-Mar-2025
G10 Phase 1: G10 Rules 6 GPU & NIC Mixing rules for NX-8150G-G10:
When GPU is FHFL GPU (A16, L40S, H100 NVL, H200 NVL, B300, RTX Pro 6000 BSE…more to come based on NVIDIA roadmap)

Table Link

NX-8150G-G10 NPI-1408 10-Mar-2025 5-Sep-2025
G10 Phase 1: G10 Rules 7 GPU & NIC Mixing rules for NX-8150G-G10:
When GPU is L4 GPU, B10 GPU

Table Link

NX-8150G-G10 NPI-1408 10-Mar-2025
G10 Phase 1: G10 Rules 8 For NX-8170-G10, If HBA is available and selected for the chosen drive configuration:
Quantity option available for all AOC NIC reduces by 1
Error message:: “Please note for All SSD drive configuration, you can select a maximum of 2 NIC cards. Switch over to All NVMe, if you want 3 NIC cards in your system.”

Example:
If HBA NOT selected
C-NIC-25G2D1 will have quantity options as 1,2 and 3 per product options available
If HBA selected
C-NIC-25G2D1 will have quantity options as 1,2 (1 less per product options available)
The above applies for all NICs supported with NX-8170-G10

For NX-8170-G10, If HBA is available and selected for the chosen drive configuration: The max quantity available for all AOC Nics is 2. This applies for all NICs.

Error message:: “Please note for All SSD drive configuration, you can select a maximum of 2 NIC cards. Switch over to All NVMe, if you want 3 NIC cards in your system.”

Example:
If HBA NOT selected
C-NIC-25G2D1 will have quantity options as 1,2 and 3 per product options available
C-NIC-100G2A2 will have quantity options as 1 and 2 per product options available

If HBA selected
C-NIC-25G2D1 will have quantity options as 1,2
C-NIC-100G2A2 will have quantity options as 1,2

NX-8170-G10 NPI-1408 10-Mar-2025 12-May-2025
G10 Phase 1: G10 Rules 9 200GbE (eg. C-NIC-200G2A1 Mellanox (CX7)) cannot be mixed with 100GbE NIC (eg. C-NIC-100G2E1, C-NIC-100G2A2)

12June25 – NIC Mixing has been added as G10 Phase 2 & Phase 3 rules – Rule 11

All G10 Platforms NPI-1408 27-Mar-2025
G10 Phase 1: G10 Rules 10 NX-8150G-G10 will support the H100 NVL GPU. 8150G-G10 will have a different OT (operating temperature) if H100 NVL GPU is selected. We will need a message in FL to trigger when the H100 NVL GPU is selected with this platform.

Message: “NX-8150G-G10 supports an ambient temperature of 25°C with C-GPU-H100-NVL”

NX-8150G-G10 NPI-1408 6-May-2025 9-Jul-2025
G10 Phase 1: G10 Rules 11 Display below message when U-GPU-H100-NVL is being quoted.

Message: “NX-8150G-G10 supports an ambient temperature of 25°C with U-GPU-H100-NVL”

NX-8150G-G10 NPI-1408 6-May-2025 9-Jul-2025
G10 Phase 2: G10 Rules 1 As specified in G10 BRD:
HBA is a selectable component in the workflow for NX-1175S-G10 , NX-3035-G10

The HBA component visibility is dependent on the drive selected.

HBA should be selectable if one of the drives is either HDD or SSD (incl. encrypted parts). HBA should NOT be selectable for All NVMe / All NVMe SED drive configuration.

NX-1175S-G10, NX-3035-G10 NPI-1439
NPI-1458
1-June-2025
G10 Phase 2: G10 Rules 3 For 1175S-G10 Hybrid configuration (NVMe + HDD) | This rule applies for RPO-1Hr, RPO-6Hr and RPO 24 – Hr
“If nodes are configured with 2 NVMe + 2 HDDs configuration, the NVMe capacity should be a minimum of 30 % or more of the overall node capacity.”
When this percentage is calculated round up the percentage to the whole number
NX-1175S-G10 Override functionality required NPI-764
NPI-1439
1-June-2025
G10 Phase 2: G10 Rules 4 For 1175S-G10: If All Flash drive configuration is chosen then minimum 4 quantity of 32GB memory must be selected

This applies to NVME and NVME SED All-Flash as well

NX-1175S-G10 NPI-764
NPI-1015
NPI-1439
1-June-2025 8-Jul-2025
G10 Phase 2: G10 Rules 5 GPU & NIC-related option constraints for Platform NX-8155AS-G10 | This rule applies to NVIDIA L4, NVIDIA A16, B10 GPUs under NVME All Flash (and all configs that allow for NIC & GPU selection)

Table Link

NX-8155AS-G10 NPI-1439 1-June-2025
G10 Phase 2: G10 Rules 8 GPU & NIC related option constraints for Platform NX-1175S-G10. Please note that these rules should apply only for Hybrid configuration

Table Link

NX-1175S-G10 NPI-1439 1-June-2025
G10 Phase 2: G10 Rules 9 GPU & NIC related option constraints for Platform NX-1175S-G10. Please note that these rules should apply only for NVME All-Flash configuration

Table Link

NX-1175S-G10 NPI-1439 1-June-2025
G10 Phase 2: G10 Rules 10 NX-8155AS-G10 – When GPU is selected, a maximum of 8 NVMe drives can only be selected.
Message : “When GPU is selected, max 8 NVMe drives are allowed”
NX-8155AS-G10 NPI-1439 1-June-2025
G10 Phase 2: G10 Rules 11 For all NX-G10 platforms, we can support multiple (heterogeneous nics) on the same platform, as long as the total nic count is within max supported quantity.
These nic-nic combinations are supported along with the specific AIOM/LOM selection as mentioned in the supported list below.

Supported NIC-NIC mixing SKUS –
1. C-NIC-25G2A2 (and C-NIC-25G2A2-Q) with C-NIC-10G4B1BT when AIOM is C-LOM-10G2B1BT
2. C-NIC-25G2A2 (and C-NIC-25G2A2-Q) with C-NIC-10G2D1BT when AIOM is C-LOM-10G2D1BT (post-GA)
3. Other heterogeneous combinations with multiple nics are not supported
4. Exception – 1175S-G10 will not support nic mixing as there is no AIOM/LOM
5. AIOM/LOMs must be homogenous
6. Every supported NIC can be homogeneous (including C-NIC-25G2A2, C-NIC-10G4B1BT, C-NIC-10G2D1BT)

For all other nic SKUs, we only support homogenous nics (no combination of multiple NIC SKUs in the same platform).

G10 platform nic mixing rules – https://docs.google.com/spreadsheets/d/1ZWHFCt5jeCPLG1DnNJtCFFJ0Syh12p-eKuHEG95vpXQ/edit?gid=512855463#gid=512855463


12-Nov-2025 update (added nic mixing combination number 2)
For all NX-G10 platforms, we can support multiple (heterogeneous nics) on the same platform, as long as the total nic count is within max supported quantity.
These nic-nic combinations are supported along with the specific AIOM/LOM selection as mentioned in the supported list below.

Supported NIC-NIC mixing SKUS –
1. C-NIC-25G2A2 (and C-NIC-25G2A2-Q) with C-NIC-10G4B1BT when AIOM is C-LOM-10G2B1BT
2. C-NIC-25G2A2 (and C-NIC-25G2A2-Q) with C-NIC-10G2D2BT when AIOM is C-LOM-10G2D1BT
3. Other heterogeneous combinations with multiple nics are not supported
4. Exception – 1175S-G10 will not support nic mixing as there is no AIOM/LOM
5. Every supported NIC can be homogeneous (including C-NIC-25G2A2, C-NIC-10G4B1BT, C-NIC-10G2D1BT)

For all other nic SKUs, we only support homogenous nics (no combination of multiple NIC SKUs in the same platform).

G10 platform nic mixing rules – https://docs.google.com/spreadsheets/d/1ZWHFCt5jeCPLG1DnNJtCFFJ0Syh12p-eKuHEG95vpXQ/edit?gid=512855463#gid=512855463

All G10 Platforms NPI-1439
NPI-1721
1-June-2025 12-November-2025
G10 Phase 2: G10 Rules 12 Below pop up message should fire only if NX-8155AS-G10 or NX-8170A-G10 platforms are quoted. The message should pop up as soon as the platform is selected while in the configuration page:
“Default rails kits for NX-8155AS-G10 or NX-8170A-G10 platforms have a longer nominal length as compared to other G10 platforms. For more information, please refer to this documentation. If a shorter rail kit is preferred then please select U-RAIL-1U-D.”

Link above will change and should be available in a few days. Putting this as placeholder meanwhile as we need the popup message to fire.

NX-8155AS-G10, NX-8170A-G10 NPI-1439 14-Jul-2025 22-Jul-2025
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 10 When NVIDIA RTX Pro 6K (C-GPU-RTXP6KBSE-96GB) is quoted with NX-9151-G9, a message should be triggered
“RTX Pro 6000 BSE GPU with the NX-9151-G9 will operate at 450W instead of its maximum 600W. As a result, you can expect a performance reduction of approximately 6–12%, depending on the workload.”

When NVIDIA RTX Pro 6K (C-GPU-RTXP6KBSE-96GB) is quoted with NX-9151-G9, a message should be triggered
“When used with the NX-9151-G9, the RTX Pro 6000 BSE GPU operates at 450W instead of its maximum 600W, which may result in an estimated performance reduction of approximately 6–12%, depending on the workload.”

NX-9151-G9 NPI-1561 21-Jul-2025 28-Jul-2025
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 11 For NX-8170-G9, NX-8150-G9, NX-8155-G9, and NX-3155-G9 , when the CPUs C-CPU-4510 or C-CPU-4509Y are added alongwith a PCIe Gen5 NVMe drive (C-NVM-3.84TB-AB-A , C-NVM-7.68TB-AB-A, C-NVM-15.36TB-AB-A) , then the following message should trigger

“PCIe Gen5 drives configured with EMR CPU 4510 or 4509Y in NX-8170-G9, NX-8150-G9, NX-8155-G9, or NX-3155-G9 will operate at PCIe Gen4 speed”

This needs to be added as the amber banner on quote screen. Additionally, it should also be displayed as a warning/popup under NVMe selection on config screen when this particular combination is selected.

NX-8150-G9, NX-8170-G9, NX-8155-G9, NX-3155-G9 NPI-1585 31-Jul-2025 4-Sep-2025
G10 Phase 3: G10 Rules 1 As specified in G10 BRD:
HBA is a selectable component in the workflow for NX-3035-G10

The HBA component visibility is dependent on the drive selected.

HBA should be selectable if one of the drives is either HDD or SSD (incl. encrypted parts). HBA should NOT be selectable for All NVMe / All NVMe SED drive configuration.

NX-3035-G10 NPI-1458 21-Aug-2025
G10 Phase 1: G10 Rules 12 When NVIDIA RTX Pro 6K (C-GPU-RTXP6KBSE-96GB) is quoted with NX-8150G-G10, the following 2 messages should be triggered
1. “When used with the NX-8150G-G10, the RTX Pro 6000 BSE GPU operates at 450W instead of its maximum 600W, which may result in an estimated performance reduction of approximately 6–12%, depending on the workload.”
2. “When the RTX Pro 6000 BSE GPU is added to NX-8150G-G10, the platform will have a max operating temperature of 25C”

When Upgrade RTX Pro 6K GPU (U-GPU-RTXP6KBSE-96GB) is selected, the following 2 messages should be triggered
1. “When used with the NX-8150G-G10, the RTX Pro 6000 BSE GPU operates at 450W instead of its maximum 600W, which may result in an estimated performance reduction of approximately 6–12%, depending on the workload. Please ensure memory quantity on the NX-8150G-G10 node is 16 or lesser if you plan to populate 2 quantity of RTX Pro 6000 BSE GPU”
2. “When the RTX Pro 6000 BSE GPU is added to NX-8150G-G10, the platform will have a max operating temperature of 25C”

This needs to be added as the amber banner message on the quote screen.

NX-8150G-G10 NPI-1626 5-Sep-2025 11-Sep-2025
G10 Phase 1: G10 Rules 13 NX-8150G-G10 with RTX Pro 6000 BSE GPU (C-GPU-RTXP6KBSE-96GB)

For NX-8150G-G10, when 24 or 32 quantity of Memory is selected, a maximum of 1x RTX Pro 6000 BSE GPU is selectable.
Error message when 2x RTX Pro 6000 BSE GPU is selected and memory quantity is 24 or 32 –
“Max 16 DIMMs allowed in NX-8150G-G10 with 2 quantity of RTX Pro 6000 BSE GPU. Alternatively, you may select 1 quantity of RTX Pro 6000 BSE GPU for higher quantity of DIMMs”

For NX-8150G-G10, when 8 or 16 quantity of memory is selected, the user can select upto 2x RTX Pro 6000 BSE GPU with no error message.

NX-8150G-G10 NPI-1626 5-Sep-2025
G9 Phase 4 | Section 4: G9 EMR+ components rules, 9151-G9 and 1150S-G9 12 To enable worldwide quotability for NX-9151-G9

For US (non-FED) and EU countries – Only PRD Support Option should be visible and selectable for NX-9151-G9
For US (FED) – Only FED PRD Support Option should be visible and selectable for NX-9151-G9
For All other countries – Only NBS support option should be visible and selectable for NX-9151-G9

Whenever NBS is quoted on NX-9151-G9, the following message should appear on Frontline
The NX-9151-G9 has “Production Level” support only in the US and EU. In other regions, hardware support level is “Next Business Day Ship”. Parts are shipped from depots outside the region, with delivery subject to shipping and customs processing times.

NX-9151-G9 NPI-1658 26-Sep-2025

Rule Generator

“Rule Generator” in Frontline CPQ (Configure, Price, Quote) is a core component within the software that allows business Product Managers to define and enforce specific rules governing how products are quoted, essentially automating decision-making based on set criteria during the quote generation process. 

  • Benefits:
    • Accuracy: Reduces errors by automatically applying rules to ensure consistent quoting validation. 
    • Efficiency: Streamlines the quoting process by eliminating manual calculations and decision-making. 
    • Flexibility: Allows businesses to adapt rules quickly to changing market conditions or customer requirements. 
    • Go-To- market: Products can be launched in market when demand is there without any delay with rules.
  • Typical Rule Types:
    • Product Selection Rules: Define which products are available based on selected attributes. 
    • Validation Rules: Check for errors or inconsistencies in a quote before submission. 
    • Discount Rules: Restrict discounts based on specific conditions. 

How it works:

  • Rule Definition:

    Users create rules within the Rule Generator platform, specifying Products, conditions (e.g., “if product type is ‘NCI’ and quantity is greater than 30”) and corresponding actions (e.g., “restrict to 10% discount”) and actions in result. Once the Rule is defined , it can be published to Dev, UAT and Production instances.

  • Frontline : Frontline would consume these rule and validate the quotes by reading these rules followed by performing the action.

    Example Use Cases:

    • Disable Quoting of a Product: A product can be sold in particular region.
    • Allowed Product Min and Max Term : Apply minimum and maximum purchase of term for a product. 
    • Allowed Product Min and Man Quantity : Apply minimum and maximum purchase of quantity for a product.
    • Restriction on applying Discount: Throw Error when the threshold of discount is passed.
    • Add a Banner Message: Frontline can show a banner message for any announcement or product End of Sale.

Steps to Define Rule: https://docs.google.com/presentation/d/12ecAqfL-FoQAZuTzpEctnJ52MOxMusjP/edit#slide=id.g337e53def89_0_81

FSN

Problem Statement: There are cases where Renewals are sold as new, but they are not identified and DNRd – causing impacts on several downstream process, like Quota, Compensation. Additionally – customers may continue to use their old licenses.

Objective: 

  • Create a proactive approach to identifying Field Selling New Opportunities.
  • Bring awareness to the account teams of products the customer already owns.
  • Force a conversation with the Account teams to work together to resolve issues.
  • Reduce  manual efforts for forecasting, SFDC hygiene and compensation adjustments.

Changes:

    • Identify FSN Quote and tag the oppty(Record Type= Sales Opportunity)  as soon as it is the identified on the Primary Quote. 
      • Create a new Picklist field on Oppty : FSN
  • LOV: 
        • Blank (Default),
        • FSN (Systematically based on Primary Quote)
        • Not an FSN,(Systematically based on Primary Quote)
        • FSN Override , (manually updated by OPS)
        • Not an FSN Override(Manually Updated by CSR /OPs)
    • Send Email notification once oppty is tagged as FSN. 
    • Send Stage 7 Automatic Email notification to CSR if FSN Opportunity Object is created. 
  • Send email notification if it moves from any stage lower to stage 7. 
  • Do not send duplicate notifications when moving from stage 7 to another Stage 7 (Order with disti  stage 7  to order with Ntnx stage 7 for example). 
  •  Stage 8 Automatic Email Notification to CSR for FSN tagged Oppty. 
  •  Stage 9 Closed Lost Email to CSR when or FSN tagged Oppty. 
  • Ensure Ops has Override capability for FSN field on oppty . 
  • Do not allow FSN field to be updated to Not an FSN or Not an FSN override if there is a mixed deal record created.

 

FY 26 Comp

 

Req # Area What How?
1 Renewals All Renewals with timeliness calculations to use new multipliers:

  • Prior Year Late: 0.5x
  • Late: 0.8x
  • On time: 1.0x
  • Early: 1.0x
  • Next Year Early: 0.5x
    Deal quality no longer considered. Compensation recalculated on Stage 8 Closed Won as today.
Timeliness is already defined in frontline, Just remove the deal quality check and update the multiplier

  • All approved inflight quotes must use the FY25 compensation, including any updates such as Primary Quote changes or additions of special instructions for any type of edits.
  • All draft inflight quotes should use the FY26 compensation.
  • The functionality for cloning approved quotes is yet to be defined.
  • Cloning should apply the FY26 compensation.
2 Renewals OEM Renewals and SaaS Renewals pay flat 1.0x multiplier (no change). No Change
3 Sales Opportunity Sales Opportunity with term L or E < 3 years: 0.9x multiplier, else 1.0x. Applies to New logos. What will happen to expand as it is not new logo?

  • All approved inflight quotes must use the FY25 compensation, including any updates such as Primary Quote changes or additions of special instructions for any type of edits.
  • All draft inflight quotes should use the FY26 compensation.
  • The functionality for cloning approved quotes is yet to be defined.
  • Cloning should apply the FY26 compensation.
4 Sales Opportunity Portfolio Product Incentive logic (4 conditions) will no longer be used for compensation.
Portfolio Product Attach % continues to be calculated/displayed in Frontline and synced to SFDC.
Term Length Ratio, High Value Service, and Pct of SW License Bundle will no longer be calculated or synced.
Comment out code for these 3 fields, do NOT delete.
Remove these 3 fields from Frontline UI.
  • Only the Portfolio Product Attach % should be available in Frontline; the other three fields should no longer be visible in the Frontline UI or backend when FY26 is applicable, and there should be no sync with SFDC for these 3 fields.
  • All approved inflight quotes must use the FY25 compensation, including any updates such as Primary Quote changes or additions of special instructions for any type of edits.
  • All draft inflight quotes should use the FY26 compensation.
  • The functionality for cloning approved quotes is yet to be defined.
  • Cloning should apply the FY26 compensation.
5 Sales Opportunity Legacy 1.0 Portfolio Opportunities & Quotes pay 1.0x multiplier. It is increased from .9X to 1.0X.

  • All approved inflight quotes must use the FY25 compensation, including any updates such as Primary Quote changes or additions of special instructions for any type of edits.
  • All draft inflight quotes should use the FY26 compensation.
  • The functionality for cloning approved quotes is yet to be defined.
  • Cloning should apply the FY26 compensation.
6 Sales Opportunity All L+E OEM pay 1.0x multiplier. No Change
7 Frontline Any code no longer needed for existing compensation logic should be commented out and NOT deleted.
8 OEM – Cisco No change to new Cisco compensation plan implemented in FY25. No Change

Commission Information (Quota Retirement Amount and Commission Multiplier will be recalculated at the time of booking).

9 Services Frontline Services only quotes will pay a flat 1.0x regardless of discounts or zone.

Quotes with both services and software skus will have a multiplier based on the deal term of the software as defined in requirement #3 above.|

Quotes with both services and software skus will have a multiplier based on the deal term of the software as defined in requirement #3 above.|

Upgrade

Q1 : What is changing and when?

A :  Effective 2nd July 2025,  

  • Mid-term upgrades to a different product will be supported.
    • For example, NCI-Data licenses can be upgraded to NCI.  
  • Frontline quoting and Quote PDF will reflect simplified SKU structure aligning with existing PnP 2.0 nomenclature.

 

Q2 : What is the simplified SKU structure for mid-term Upgrades?

A :   Upgrade SKUs will only reflect the end state of the upgrade. For example, all upgrades to NCI Ultimate, Mission critical support will use the same SKU :  ‘USW-NCI-ULT-MC’ .  

Base License Upgrades To Existing Upgrade SKU New Upgrade SKU
NCI-PRO-PR    NCI-ULT-MC USW-NCI-PRO-PR-2-ULT-MC USW-NCI-ULT-MC
NCI-D-PRO-PR NCI-ULT-MC Path not available
NCI-E-PRO-PR NCI-ULT-MC Path not available

 

Q3 : How does the new SKU structure align with PnP 2.0 nomenclature?

 A:   As an example, for NCI Ultimate Mission Critical  –

  • Land & expand Deals :  SW-NCI-ULT-MC
  • Renewals : RSW-NCI-ULT-MC
  • Any mid-term upgrade to NCI ULT mission critical : USW-NCI-ULT-MC

 

Q4 : How do these changes impact deals in Flight?

 A:  From 7/2/2025 – all new SW Upgrade quotes will reflect simplified SKU structure.

      For Deals in flight :  

  • SW Upgrade quotes (using Old SKUs) in DRAFT/ In Review status will be marked VOID. Fresh quotes need to be created (using new SKUs) for these upgrades.
  • APPROVED quotes (using Old SKUs)  are valid till expiry and POs continue to be accepted.

 

Q5 : What changes are being made to the SW Upgrade Quote PDF?

A :  Following updates are being made to the Quote PDF : 

  • Quote PDF will reflect simplified SKU structure (new SKUs)  starting 7/2/25.
  • ‘Special instructions’ section in the Quote PDF will capture details of the license being upgraded. For additional details, refer to the Quoting Guidelines.

Definitions

Q6 : What is a ‘Base License’?

A :  License being upgraded to a higher tier is referred to as Base License.

 

Q7 : What is an ‘Upgrade License’?

A :  License deposited on a higher tier is referred to as an Upgrade License.

 

Q8 : What is a mid-term Upgrade?

A :  If an upgrade action is performed before the license expires, it is referred to as  mid term  upgrade. 

 

Q9 : What does mid-term Upgrade on the same product/ different product mean?

A :  

  • Same product Upgrades : Customers can upgrade to a higher License tier or Support Level or both for the same product. Example : NCI-PRO-PR upgrades to NCI-PRO-MC
  • Upgrades to a different product : Customers can upgrade to a different product. Example : NCI-D-PRO-PR upgrades to NCI-PRO-MC

 

Products and Upgrade paths

Q10 : What products can be upgraded?

A :  SW Upgrades can be quoted for the following PnP 2.0 products :

  • NCI , NCI Data , NCI Edge , NCI-C , EUC
  • NCM, NCM User , NCM Edge
  • NDB , NUS
  • NKP, NKP-FS , NDK
  • NAI, NAI-GPT

 

Q11 : What are the upgrade paths available for each product?

A :  Please refer to the APPENDIX  for details of SW Upgrade paths available for each product.

 

Q12 :  Are SW upgrades for the NCP (Nutanix Cloud Platform) bundle supported?

A :  Yes, NCI and NCM from the NCP bundle can be upgraded independently.

Q13 : Can customers upgrade to a product that is on a different meter (VM to core, user to core)?

A :  Yes, customers can upgrade to a product that is on a different meter.

Upgrade example Meter change Meter Ratio Base license upgrades to
NCI to NDB core to core 1 : 1      1 NCI core upgrades to  1 NDB core
EUC to NCI User to core 1 ​ : 1      1 EUC user upgrades to 1 NCI core
NKP to NKP-FS vCPU to core 1 ​ : 1      1 NKP vCPU upgrades to 1 NKP-FS core
NCI Edge to NCI VM to core 1 ​ : 2     1 NCI Edge VM upgrades to 2 NCI cores

Please refer to the APPENDIX for details of SW Upgrade paths available for each product.

 

SW Upgrade Scenarios

Q14 : Are partial Upgrades supported?

A :   Yes , partial upgrades of the Base License are supported , provided the base license has quantity available for upgrade. Multiple partial upgrades can be quoted for a base license on the same quote or via different quotes.

 

Q15 : Can I mix  – same product and different product upgrades for the same base license?

A :  Yes , the same base license can be upgraded partially to –

  • A different product OR
  • Higher License tier or Support level or both on the same product. 

 

Q16 : Can a converted license be upgraded?

A :  Yes , licenses created through conversion can be upgraded. Illustrated through an example :

  • CBL AOS license was converted to NCI.
  • The NCI license is eligible for SW Upgrade.

 

Q17 : Can I upgrade a license that is already renewed?

A :  Yes , such upgrades are also considered mid-term upgrades,

 

Q18 : Is it possible to further upgrade an Upgraded License?

A :  Yes , Upgrade of an Upgrade license will be supported.

  • Customer upgrades NCI STR to NCI PRO license tier.
  • NCI PRO can now be upgraded to NCI Ultimate tier or to a different product (NDB/ NKP-FS).

Q19 : Can I upgrade a license at renewal?

A :  No, currently we do not support Upgrades at the time of renewal. Only mid-term upgrades are possible.

 

Q20 : Can I upgrade a base license that has a future start date?

A :  Yes, base licenses with a future start date can be upgraded. Note that the start date of the SW Upgrade has to be post the start date of the base license.

 

Q21 : Can I extend the term of my Upgrade License?

A :  Upgrade license and Base license are co-termed. The end date  of the Upgrade license is the same as the end date of Base license.

 

Q22 : Can OEM partners quote mid-term upgrades?

A :  No, mid-term upgrades are not supported for licenses sold by our OEM partners (Cisco, Dell, Lenovo, Fujitsu, HPE GL). 

 

SW Upgrades Pricing

Q23 : How are SW Upgrades priced?

 A :   List price of Upgrade SKU in the pricebook is same as the 3YR list for Land & expand SKU.

         Frontline prorates list price calculation for SW Upgrades. 

         Ex: Customer upgrades NCI PRO production to NCI Ultimate Mission Critical tier for 225 days.

Steps Detail Formula V5 Price book
1 3YR price for upgrade  3YR price of Upgrade Tier – 3YR price of Base Tier 1892 – 1300 = 592
2 1YR price of upgrade 3YR price of upgrade * 0.3334 592 X 0.3334 = 197.37
3 List price for upgrade term 1YR price of upgrade * Upgrade term / 365 197.37 * (225 / 365) = 122

 

Q24 : What is the recommended discount for an Upgrade quote?

A :   Frontline calculates recommended discount for Upgrade quote based on historical purchase.

 

SW Upgrades Licensing Mechanism 

Q25 : What happens to the Base license after an upgrade?

A :  Once a Base license is fully upgraded, it is marked DNR (Do not renew) and the ATR for this license is no longer valid. The asset is also invalidated.

 

Q26 : Does each Upgrade action trigger new license creation?

A :  Yes, each upgrade action triggers  the creation of a new license and associated asset. 

 

Q27 : Can an upgrade license be directly applied to a cluster?

A :  Yes, SW Upgrade licenses can directly be applied to clusters and clusters get licensed on the higher tier . There is no need to apply both the Base license and Upgrade license together.

 

Q28 : When is an upgrade license available for application?

A :  Upgrade licenses are available for application on their start date when –

  • The base license is unlicensed from a cluster and license quantity is returned.
  • If the base license is still applied to a cluster, the Upgrade license is in ‘pending return’ state and cannot be utilized until the base license is unlicensed.

 

Renewals and ATR

Q29 : What happens to the ATR associated with the Base License?

A :  Following changes happen to the ATR of the Base license :

  • On partial Upgrade of Base License : ATR is updated to reflect expected ACV at renewal of the remaining quantity after upgrade
  • On full Upgrade of Base License : ATR of base license is no longer valid.

 

Q30 : What happens to the ATR associated with the Upgrade License?

A :  Each Upgrade action triggers the creation of a New ATR for upgrade license.

 

Quoting Guidelines

Q31 : What quote type should be selected for quoting ‘SW Upgrades’?

A :  Following attributes have to be selected while creating an Upgrade quote : 

  • Quote Type = ‘Upgrade’
  • Product Portfolio – ‘New Portfolio’

 

Q32 : How do I select a different product or higher tier for upgrades on Frontline?

A :   Click on ‘Add Product’ and then : 

Step 1 : Enter License Number to be updated. Frontline shows current details and possible upgrade paths.

Step 2 : Choose upgrade path, upgrade quantity and start date for the upgrade license..

Q33 : Can you share a sample of the Nutanix quote PDF to partners?

           

 

Q34 : My partner/customer wants information about the Base license from Quote PDF?

A :  Special Instructions section on Quote PDF captures information about the base license :                                         

                         

APPENDIX

SW Upgrade paths to Different Product

Product Upgrades To Meter Upgrade path for 

License Tier

Upgrade path for 

Support Level

NCI (1)(1) :Regular and NCP-NCI NDB 1 core 

: 

1 core

STR/PRO/ULT—> NDB PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

NKP-FS STR—> STR/PRO/ULT

PRO—> PRO/ULT

ULT—> ULT

SEC—> SEC

ADR—> ADR

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

AP—> AP/AM

AM—> AM

NAI-GPT STR—> PRO/ULT

PRO—> PRO/ULT

ULT—> ULT

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

AP—> AP/AM

AM—> AM

NCI Data NCI 1 core 

: 

1 core

STR—> STR/PRO/ULT

PRO—> PRO/ULT

ULT—> ULT

SEC—> SEC

ADR—> ADR

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

AP—> AP/AM

AM—> AM

NDB STR/PRO/ULT—> NDB PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

NCI Edge NCI 1 VM

: 

2 cores

STR—> STR/PRO/ULT

PRO—> PRO/ULT

ULT—> ULT

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

AP—> AP/AM

AM—> AM

NCI-C NCI 1 core

:

1core

STR—> STR/PRO/ULT

PRO—> PRO/ULT

ULT—> ULT

SEC—> SEC

ADR—> ADR

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

Product Upgrades To Meter Upgrade path for 

License Tier

Upgrade path for 

Support Level

EUC NCI 1 user 

:

1 core

STR—> STR/PRO/ULT

PRO—> PRO/ULT

ULT—> ULT

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

AP—> AP/AM

AM—> AM

NKP NKP-FS 1 vCPU

:

1 core

PRO—> PRO/ULT

ULT—> ULT

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

AP—> AP/AM

AM—> AM

NAI-GPT 1 vCPU

:

1 core

PRO—> PRO/ULT

ULT—> ULT

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

AP—> AP/AM

AM—> AM

NKP-FS NAI-GPT 1 core

:

1core

STR—> PRO/ULT

PRO—> PRO/ULT

ULT—> ULT

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

AP—> AP/AM

AM—> AM

NCM Edge NCM 1 VM

:

2 cores

STR—> STR/PRO/ULT

PRO—> PRO/ULT

ULT—> ULT

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

AP—> AP/AM

AM—> AM

NCM User NCM 1 user

:

1 core

STR—> STR/PRO/ULT

PRO—> PRO/ULT

ULT—> ULT

PR—> PR/MC/FP/FM

MC—> MC/FM

FP—> FP/FM

FM—> FM

AP—> AP/AM

AM—> AM

 

SW Upgrade paths to Higher Tier on Same Product

Product Upgrade Type Meter Upgrade path for 

License Tier

Upgrade path for 

Support Level

NCI(1)

NCI Data

NKP-FS

(1) :Regular  and NCP-NCI

Support Only 1 core 

: 

1 core

STR/PRO/ULT/SEC/ADR PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

License Only STR—> PRO

STR—> ULT

PRO—> ULT

PR/MC/FP/FM/AP/AM
License + Support STR—>PRO/ULT

PRO—>ULT

PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

NCM(1)

(1) :Regular and NCP-NCM

Support Only 1 core 

: 

1 core

STR/PRO/ULT/SS addon PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

License Only STR—> PRO

STR—> ULT

PRO—> ULT

PR/MC/FP/FM/AP/AM
License + Support STR—>PRO/ULT

PRO—>ULT

PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

NCI Edge

NCM Edge

Support Only 1 VM 

: 

1 VM

STR/PRO/ULT PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

License Only STR—> PRO

STR—> ULT

PRO—> ULT

PR/MC/FP/FM/AP/AM
License + Support STR—>PRO/ULT

PRO—>ULT

PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

Product Upgrade Type Meter Upgrade path for 

License Tier

Upgrade path for 

Support Level

EUC

NCM User

Support Only 1 user

: 

1 user

STR/PRO/ULT PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

License Only STR—> PRO

STR—> ULT

PRO—> ULT

PR/MC/FP/FM/AP/AM
License + Support STR—>PRO/ULT

PRO—>ULT

PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

NDB Support Only 1 core 

:

1 core

NDB Platform PR—> MC/FP/FM

MC—> FM

FP—> FM

NUS Support Only 1 TiB

: 

1 TiB

STR/PRO/ADR/SEC PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

License Only STR—> PRO PR/MC/FP/FM/AP/AM
License + Support STR—>PRO PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

NKP Support Only 1 vCPU

: 

1 CPU

PRO/ULT PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

License Only PRO—> ULT PR/MC/FP/FM/AP/AM
License + Support PRO—>ULT PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

Product Upgrade Type Meter Upgrade path for 

License Tier

Upgrade path for 

Support Level

NAI-GPT Support Only 1 core

: 

1 core

PRO/ULT PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

License Only PRO—> ULT PR/MC/FP/FM/AP/AM
License + Support PRO—>ULT PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

NAI Support Only 1 vCPU : 1vCPU

1GB : 1GB

PRO PR—> MC/FP/FM

MC—> FM

FP—> FM

AP—> AM

NCI-C Support Only 1 core 

: 

1 core

STR/PRO/ULT/SEC/ADR PR—> MC/FP/FM

MC—> FM

FP—> FM

License Only STR—> PRO/ULT

PRO—> ULT

PR/MC/FP/FM
License + Support STR—>PRO/ULT

PRO—>ULT

PR—> MC/FP/FM

MC—> FM

FP—> FM

NDK Addon Support Only 1 core 

: 

1 core

NDK PR—> MC/FP/FM

MC—> FM

FP—> FM

NKP C8 Support Only 1 vCPU 

: 

1 vCPU

ULT PR—> MC/FP/FM

MC—> FM

FP—> FM

 

Exception Based Pricing

The objective of Exception Based Price Quoting is to offer a feature in Frontline to Auto Approve the Non DR partner’s quote with eligible discount.

In Exception Based Price Quoting, Frontline will ensure DR policies inside Exception Based Pricing scenarios are upheld automatically resolving potential legal issues, eradicating errors, and decreasing the number of quotes requiring lengthy research, review, and approval cycles. Additionally, ensure the ExceptionDiscounting only with a DR policy is automatically upheld in a quote.

Key Features:

  • Exception Based Price on a quote would trigger only when a non DR quote has been applied a discount greater than desired discount to be given.
  • Once the system finds the discount is higher than desired discount , Frontline’s exception pricing discount rules triggers to correct discount and Auto Approve the quote.
  • When a Non DR quote is compared against a DR quote in opportunity, multiple factors considers like product, Quantity , Term , a valid DR , license and supportagainst the DR quote,
  • A Non DR quote will also be “Auto Rejected” when it does not meet the rules of exception based pricing against a DR quote,
  • In addition Frontline has automated the PIF discount to be updated  in a Non DR quote. 

Key Benefits:

  • Improved Turnaround Time: With instant quote dispositions, the automation allows for faster quote processing and delivery to customers.
  • Enhanced Accuracy: The system ensures that all discounts adhere to the allowable discount levels, eliminating confusion and preventing approval errors.
  • Streamlined Process: By automating the approval process for non-DR quotes, we can reduce manual intervention and expedite the overall workflow.

We are confident that this new feature will provide a more efficient and seamless experience for our users. Stay tuned for more updates as we continue to enhance our systems.

         

Automating the quote approval process for non-DR quotes will enhance the user experience by providing instant quote dispositions, allowing for faster turnaround and delivery to customers. This automation ensures accuracy in allowable discount levels, eliminating confusion and preventing approval errors that could violate a DR holder’s discount advantage.

All exception-based pricing requires a deal registration, In Phase 2 of quote automation, launching on February 05, 2025, the focus will be on automating non-DR quotes under opportunities with an approved deal registration.

Exception priced quotes under opportunities without an approved deal registration will continue to be routed to quote approvers, with guidance to reject the quote unless it qualifies for an allowable exception. Auto-rejection of these quotes will be automated in the next phase of quote automation.

Discounting Methodology for Non-DR Quotes

Non-DR exception discount approval is variable, based on the software discounts of the approved DR Quote

  • All distributors have access to standard non-DR discounts, which are determined by the zone and term bucket of the software.
  • When a DR quote is approved for exception pricing, non-DR quotes with the same configuration are also permitted to enter into exception pricing, following the discount advantage guidelines.
  • The permissible discount level for non-DR quotes is determined by the discount advantage guidelines outlined for deal registration.
  • To view the permissible software and PIF discount levels for non-DR quotes, please refer to the Distributor Transfer Pricing for PnP 2.0 SPOT page. Discounts are listed by term bucket and price zone.
  • The Non-DR exception pricing automation is based on NCP (2.0) software SKUs, NX HW Support and the platform integration fee (PIF) on NX & DX quotes
  • Legacy products and services SKUs follow standard quote approval routing

Discount Guidelines for Non-DR Quotes

Automated Quote Comparison – Product, SKU, Qty and Term

  • During the quote process, the deal registration must be valid and approved
  • The BOM is compared first on configuration (SKUs), followed by quantity and then term bucket
  • When there are multiple DR quotes with similar configurations, the automation will use the quote with the highest overall discount to compare the Non-DR thresholds against (see here for example)
  • When a DR quote has multiple quote lines for the same SKU with different discounts, automation will use the lowest discount to calculate the Non-DR discount threshold (see here for example)
  • Every quote line is individually compared against the following scenarios

Auto Approved Quotes

  • Same BOM: Number of unique software products on both quotes are the same
  • Same SKUs: The Unique software product License tier and support type on the quotes are the same
  • Same Quantity
  • Two Term Buckets at a line level: 1 to 35 months (1) and 36 or greater (2)
    • Non-DR quotes with Term Bucket 2 can be approved against Term Bucket 1 but not vice versa
  • Discounts on the Non-DR quote must adhere to or be below the discount advantage guideline
    • When the SKU, quantity, and term on the non-DR quote match the DR quote, but the discount on the non-DR quote exceeds the discount advantage guideline, the system will automatically adjust the discount to the acceptable level and proceed to auto-approve the non-DR quote

Quotes Routed for Approval

  • Non-DR quotes that meet the auto-approval criteria but are missing a required services SKUs will be routed for approval review instead of auto approving
    • Any discount adjustment required for auto-approval will be made before the quote is routed for approval review
  • Non-DR quotes that meet the auto-approval criteria but have a Sales Program on the Opportunity will be routed for approval review instead of auto approving
    • Any discount adjustment required for auto-approval will be made before the quote is routed for approval review
  • Quotes identified on the exclusion list will be routed for approval (see Exclusions and Exceptions section below)
  • Quotes with an exception selected will be routed for approval (see Exclusions and Exceptions section below)

Auto Rejected Quotes

Exception-based pricing quotes will be automatically rejected if they do not meet the qualifications outlined in the guardrails or the following scenarios.

  • Auto-rejection will be a quote status (e.g., Approved, Expired, Void, etc.)
  • Auto-rejection will be included in the quote history tracking in Frontline
  • Auto-rejection is recorded as a “System Rejection” rather than an “ApproverRejection”
  • Users cannot manually tag a quote with’Auto-Rejection’ status
  • During cloning, if the original quote is in ‘Auto-Rejection’ status, the new cloned quote will be in Draft status.
  • When a quote is auto-rejected, a pop-up message will appear in Frontline to the quote submitter —regardless of channel, internal, quote creator/editor, etc. Additionally, an email notification will be sent.

Platform Integration Fee (PIF) – Quote Discounting

Standard Discount Quotes: PIF Discount = 0%

Exception Discount Quotes: PIF Discount = Variable (Based on the software discount)

To view the permissible software and PIF discount levels for non-DR quotes, please refer to the Distributor Transfer Pricing for PnP 2.0 SPOT page. Discounts are listed by term bucket and price zone.

Exclusions and Exceptions

The following types of quotes are automatically recognized in our system and do not require discount advantage discounting rules for exception pricing.

These exception priced quotes will continue to go through the approval process for review.

Quote TypesAccount TypesPublic Sector
Renewals QuotesInternal Orders QuotesQuotes for Public Sector, Public Tender (end user account that has“Public Sector” in the account segmentation field & the Opportunity RFX box is checked)
Upgrade QuotesDirect Customer Quotes
OEM Quotes 

Exceptions

Exception requests can be made for the following quote scenarios

In Frontline draft quotes, users can choose from the following exception reasons using a dropdown field to route the quote for approval review

Related Resources

Distributor Transfer Pricing for PnP 2.0Internal resource

Platform Integration Fee Internal resource

Performance+ Deal Registration Program Internal resource

Slack Channel: #non-dr-quote-automation Internal resource