Predictika · Network visibility orders

An AI sales agent's nGenius 7000 Series switch order, checked before it goes out

An AI sales agent prepares an order for nGenius 7000 Series Packet Flow Switches for a fictional hosting company: the switch model, the ports at each speed with any breakout, features such as time stamping and L2GRE tunnels, the power input, bypass segments and how many switches are planned as one mesh. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the figures NETSCOUT publishes in the nGenius 7000 Series data sheet and returns a verdict, every reason and the figures it computed.

Scope: nGenius 7000 Series packet flow switch orders: model, ports and breakout, features by model, power input, bypass and pfsMesh size, from the public data sheet. See everything this validator covers

This validator models an order for the five PFS appliances in the nGenius 7000 Series data sheet (7010, 7030-56X, 7030-32X, 7120 and 7040-32D), not just the scenarios shown below.

  • Model and ports — each model has a fixed number of SFP-type cages and QSFP-type cages; 25G ports, 100G ports and 400G ports are available only on the models whose cages support them, and a breakout cage gives four ports, up to a model-specific number of breakout cages.
  • Port speed groups — on the PFS 7030-56X the SFP28 port speeds are assigned in groups of 4, so the 1G, 10G and 25G counts must each be a multiple of 4; 1G fiber that is not connected to TAPs goes to a person.
  • Features by model — packet time stamping, packet slicing, Packet Conditioning Engine ports, VN-tag stripping, L2GRE tunnels and MPLS header stripping are each available on some models only, and one External PowerSafe TAP chassis covers up to 8 network segments.
  • Power, mesh and stated figures — AC supplies take 100 to 240 VAC, the PFS 7040-32D needs 200 VAC or more for supply redundancy at full load, one pfsMesh holds up to 256 switches, and the ports per switch the order states must equal the configuration.

Any 7000 Series order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (NETSCOUT does not publish list prices for these switches, so this page shows no price build-up), transceiver and cable choices, software licensing, the Dell and Edgecore hardware variants, 1G ports on the QSFP-only models, and other NETSCOUT products.

The AI sales agentBuilds the order from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
Port counts that depend on the model and on breakoutOnly with workarounds
Each model has its own cages, its own breakout limit and its own supported speeds, so a rules-based CPQ needs a table or a rule for every model and every speed, edited on every data sheet update.		The cages used, the breakout cages and the speeds are computed against the model on every call.
Features that exist on some models onlyOnly with care
A feature is valid only on some models, and the models are chosen in a different step, so the two must be checked against each other in either order.		Model and each requested feature are compared together, in any order.
Port speeds set in groups of 4Only with workarounds
A rule that each count must be a multiple of 4 on one model only usually needs a custom check.		The counts are tested on every call for the model that has the restriction.
Stated ports against the configurationOnly with care
The ports per switch in the quote must equal the sum across cages and breakout, which needs a calculation before the rule can fire.		The total is computed and compared with the stated figure on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order is saved or a step is completed, so a person often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

    
1Native 25G ports are available on the SFP28 cages of the PFS 7030-56X only; other models provide 25G through breakout.
2The PFS 7010 has QSFP+ cages (40G); it has no 100G ports.
3The PFS 7010 has QSFP+ cages, which break out to 10G only; 25G breakout needs QSFP28 or QSFP-DD cages.
4The quote breaks out 7 cages; this model allows at most 6.
5The quote uses 7 QSFP-type cages for 40G, 100G, 400G and breakout; this model has 6.
6The quote has 52 1G, 10G or 25G ports on SFP-type cages; this model has 48 such cages.
7The quote uses 9 QSFP-type cages for 40G, 100G, 400G and breakout; this model has 8.
8The quote breaks out 9 cages; this model allows at most 8.
9On the PFS 7030-56X the SFP28 port speeds are assigned in groups of 4; the 1G, 10G and 25G counts must each be a multiple of 4.
10The quote has 4 1G, 10G or 25G ports on SFP-type cages; this model has 0 such cages.
11The quote uses 33 QSFP-type cages for 40G, 100G, 400G and breakout; this model has 32.
12100G breakout comes from the QSFP-DD cages of the PFS 7040-32D only.
13The quote breaks out 21 cages; this model allows at most 20.
14400G ports are available on the PFS 7040-32D only.
15Packet time stamping is available on the PFS 712x, 703x and 704x only; the PFS 7010 does not have it.
16VN-tag stripping is not available on the PFS 703x and 704x.
17Packet slicing is available on the PFS 703x and 704x only.
18The quote has 3 PCE ports; the PFS 7120 has 2.
19Packet Conditioning Engine ports are supported only on the PFS 7120.
20L2GRE tunnel origination and termination, and L2GRE header stripping, are not available on the PFS 704x.
21MPLS header stripping is not available on the PFS 704x.
22The quote asks for bypass on 9 network segments; one External PowerSafe TAP chassis per switch covers up to 8.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Features and power on the 7040-32D: A 7040-32D order with L2GRE tunnels, MPLS stripping and a 120 volt supply

    
The agent's request. Please quote 4 PFS 7040-32D switches, each with 16 400G ports and 16 100G breakout cages (64 ports). Features wanted: L2GRE tunnels, MPLS header stripping. Power is AC at 120 volts, with redundant supplies at full load. The quote states 80 ports per switch. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • L2GRE tunnels not on the 704x. L2GRE tunnel origination and termination, and L2GRE header stripping, are not available on the PFS 704x.
    • 
      
  • MPLS header stripping not on the 704x. MPLS header stripping is not available on the PFS 704x.
    • 
      
  • 7040-32D needs 200 VAC for redundant supplies at full load. The PFS 7040-32D requires an input of 200 VAC or more for power supply redundancy at full load; the supply is 120 volts.
    • 
    

    
2. Features and power on the 7040-32D: The agent resubmits after fixing the errors

    
The agent's request. Please quote 4 PFS 7040-32D switches, each with 16 400G ports and 16 100G breakout cages (64 ports). Features wanted: none. Power is AC at 208 volts, with redundant supplies at full load. The quote states 80 ports per switch. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 4 switches, 80 ports per switch, port capacity 12800 Gbps of the 12800 Gbps rated throughput.
    • 
    

    
3. Model, ports and bypass: A 7010 order with 25G ports, time stamping and 10 bypass segments

    
The agent's request. Please quote 3 PFS 7010 switches, each with 40 10G ports, 8 25G ports and 6 40G ports. Features wanted: packet time stamping, External PowerSafe TAP bypass on 10 segments. Power is AC at 230 volts. The quote states 54 ports per switch. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • 25G ports need the SFP28 cages of the 7030-56X. Native 25G ports are available on the SFP28 cages of the PFS 7030-56X only; other models provide 25G through breakout.
    • 
      
  • Packet time stamping not on the 7010. Packet time stamping is available on the PFS 712x, 703x and 704x only; the PFS 7010 does not have it.
    • 
      
  • Too many External PowerSafe TAP segments. The quote asks for bypass on 10 network segments; one External PowerSafe TAP chassis per switch covers up to 8.
    • 
    

    
4. Model, ports and bypass: The agent resubmits after fixing the errors

    
The agent's request. Please quote 3 PFS 7030-56X switches, each with 40 10G ports, 8 25G ports and 6 40G ports. Features wanted: packet time stamping, External PowerSafe TAP bypass on 8 segments. Power is AC at 230 volts. The quote states 54 ports per switch. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 3 switches, 54 ports per switch, port capacity 840 Gbps of the 2000 Gbps rated throughput.
    • 
    

    
5. Port groups and 1G fiber: A 7030-56X order with port counts that are not groups of 4 and 1G fiber

    
The agent's request. Please quote 12 PFS 7030-56X switches, each with 6 1G ports, 20 10G ports, 20 25G ports and 8 100G ports. Features wanted: none. Power is DC. 6 of the 1G fiber ports are not connected to TAPs. All the switches are planned as one pfsMesh. The quote states 54 ports per switch. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • SFP28 speeds are set in groups of 4. On the PFS 7030-56X the SFP28 port speeds are assigned in groups of 4; the 1G, 10G and 25G counts must each be a multiple of 4.
    • 
      
  • 1G fiber on the 7030-56X is for TAPs. 6 1G fiber ports on the PFS 7030-56X are not connected to TAPs; the data sheet says 1G fiber auto-negotiation is not supported there and use should be limited to TAPs, so a person should confirm.
    • 
    

    
6. Port groups and 1G fiber: The agent resubmits after fixing the errors

    
The agent's request. Please quote 12 PFS 7030-56X switches, each with 8 1G ports, 20 10G ports, 20 25G ports and 8 100G ports. Features wanted: none. Power is DC. 4 of the 1G fiber ports are not connected to TAPs. All the switches are planned as one pfsMesh. The quote states 56 ports per switch. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • 1G fiber on the 7030-56X is for TAPs. 4 1G fiber ports on the PFS 7030-56X are not connected to TAPs; the data sheet says 1G fiber auto-negotiation is not supported there and use should be limited to TAPs, so a person should confirm.
    • 
      
  • Order summary. 12 switches, 56 ports per switch, port capacity 1508 Gbps of the 2000 Gbps rated throughput.
    • 
    

    
7. Port groups and 1G fiber: The agent resubmits after fixing the errors

    
The agent's request. Please quote 12 PFS 7030-56X switches, each with 8 1G ports, 20 10G ports, 20 25G ports and 8 100G ports. Features wanted: none. Power is DC. All the switches are planned as one pfsMesh. The quote states 56 ports per switch. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 12 switches, 56 ports per switch, port capacity 1508 Gbps of the 2000 Gbps rated throughput.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares an order for nGenius 7000 Series Packet Flow Switches for a fictional hosting company: the switch model, the ports at each speed with any breakout, features such as time stamping and L2GRE tunnels, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the figures NETSCOUT publishes in the nGenius 7000 Series data sheet and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote 4 PFS 7040-32D switches, each with 16 400G ports and 16 100G breakout cages (64 ports). Features wanted: L2GRE tunnels, MPLS header stripping. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with three findings, all in one answer. L2GRE tunnel origination and termination, and L2GRE header stripping, are not available on the PFS 704x. MPLS header stripping is not available on the PFS 704x. The PFS 7040-32D requires an input of 200 VAC or more for power supply redundancy at full load; the supply is 120 volts.
    6. 
      
  6. The validator returned three blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
    7. 
      
  7. What this shows: for port counts that depend on the model and on breakout, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the AC supply to 208 volts. It removes the L2GRE tunnels and MPLS header stripping.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All three earlier findings are cleared.
    13. 
      
  13. Three problems caught in one call, fixed in one pass, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    14.