① Journal · Broadcom NetMaster
NetMaster is a suite, and suites are renewed whole even when half the components sit idle. What moves the number is scope: which components you actually run, where they overlap other tools, and where SNA has quietly faded. Here are five levers that commonly move a Broadcom (CA) NetMaster number, and how to build each.
NetMaster is renewed whole. It should be scoped to what you run.
NetMaster is the Broadcom (CA) network management portfolio for the mainframe, spanning Network Management for TCP/IP, Network Management for SNA, and Network Automation, and now positioned inside Broadcom's broader observability line. It monitors TCP/IP stack performance, SNA and VTAM sessions, TN3270 connections and file transfers, and pinpoints network slow downs across the z/OS estate. Like most suites, it is commonly renewed as a single block, even when an estate actively uses only part of it and the SNA footprint has shrunk for years.
Broadcom mainframe software is commonly licensed on capacity in MSU (Million Service Units), frequently inside a portfolio or consumption arrangement. For a suite like NetMaster, the strongest levers are scope and overlap: the components you genuinely run, and where their function is already covered by other observability tooling. Read this with our explainer on Broadcom Mainframe Consumption Licensing (MCL) and the Broadcom (CA) publisher hub.
NetMaster renewal levers · what moves the number and how it works
| Lever | What moves the number | How to build it |
|---|---|---|
| Suite scoping | Dropping unused components removes charge you earn nothing on | Map live usage against entitlement, component by component |
| Observability overlap | Functions another tool covers are candidates to scope out | Document where existing monitoring already does the job |
| Sub-capacity MSU | A lower measured capacity lowers the charge it sits on | Validate the capacity NetMaster is actually priced against |
| The consumption baseline | An MCL base set on real usage caps the recurring number | Check the consumption base was not set at a transient peak |
| The SNA decline | A shrinking SNA footprint justifies dropping that component | Evidence the SNA reduction, do not merely assert it |
These are patterns and levers we commonly observe on Broadcom NetMaster renewals, not statements of Broadcom policy or guaranteed outcomes. Your specific entitlement, pricing model, and contract terms govern; treat them as the analysis to build, validated against your own usage and contract data.
NetMaster spans TCP/IP, SNA and automation components, and the renewal commonly carries all of them regardless of what runs. Map live usage against entitlement: which components feed active dashboards and alerting, and which were enabled and forgotten. The components that earn nothing are charge you can decline at renewal. Scope discipline on a suite commonly moves the number further than any headline discount on the whole.
Renew the components you run, not the whole suite by habit.
NetMaster's network monitoring frequently overlaps mainframe operational intelligence tooling and the distributed observability platforms an enterprise already runs. Document that overlap function by function: where another tool already delivers the visibility, the NetMaster component is a candidate to scope out rather than renew. Genuine, documented duplication gives the conversation a floor; a vague claim that things overlap does not.
Documented overlap is a floor; asserted overlap is noise.
SNA and VTAM footprints have shrunk across most estates as workload moved to TCP/IP, and NetMaster's SNA component often monitors a shadow of what it once did. The lever is evidence, not assertion: session counts, trends, and the applications that have already migrated. A documented SNA decline justifies dropping or shrinking that component at renewal. The reduction you can prove is the reduction the vendor has to price.
Prove the SNA decline, and the SNA component becomes negotiable.
④ Where the NetMaster number is won
The NetMaster number moves on scope and overlap. Renew what runs, map the duplication. Evidence the SNA decline, do not assert it.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
The suite scope. NetMaster spans TCP/IP, SNA and Network Automation components, and most estates carry the full set while using a subset. Mapping live usage against entitlement, then declining to renew components that earn nothing, moves the number more reliably than a discount ask. The sub-capacity MSU it is measured on is the second lever.
Commonly. It now sits inside Broadcom's observability portfolio, and its network monitoring overlaps mainframe operational intelligence tooling and distributed observability platforms an enterprise already runs. Mapping that overlap honestly identifies components to scope out. See Ironstream and the observability licensing angle.
Twelve to eighteen months before expiry. Mapping usage across the suite, documenting overlap, and evidencing the SNA decline all take time. A renewal opened late renews the full suite by default. See how vendors time renewal pressure.
Renewing the whole suite by habit, ignoring overlap with monitoring they already pay for, and asserting an SNA decline without evidencing it. Our license negotiation service scopes the suite to live usage, and our Broadcom (CA) renewal advisory documents the overlap and the SNA trend.
Related: Broadcom MCL explained · CA 11 renewal negotiation · CA Panvalet renewal negotiation · Broadcom (CA) renewal advisory · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →