SONiC Export RFQ

Prepare a SONiC switching RFQ for international supply

The technical, operational and export fields an international buyer should provide when requesting a SONiC switching configuration from Australia.

Platform tuple

Switch model, ASIC, optics, NOS image, feature set and support path are treated as one compatibility decision.

Operations tuple

Management, telemetry, automation, configuration ownership, upgrade and rollback expectations are stated up front.

Evidence request

The buyer names which link, image, telemetry, traffic or recovery checks must be recorded before shipment.

Export gate

Destination, end user, end use, product scope and required documentation are reviewed per order.
XS-DC-32X100-LS-G1 switch front panel catalogue image
Representative xSONiC catalogue hardware: XS-DC-32X100-LS-G1 This is a catalogue product image, not a photograph of a team, facility, laboratory test, shipment, or customer deployment. It does not establish origin, compatibility, acceptance, or project delivery.

Evidence boundary

SONiC compatibility requires an exact platform-and-image record.

The switch photograph is a catalogue reference, not evidence that a particular SONiC distribution, image, feature set, optic or automation workflow has been qualified for an international order.

What establishes a project-specific claim

  • The exact switch, ASIC, optics, SONiC image, release and required feature matrix
  • The agreed configuration, telemetry, automation, upgrade, rollback and support ownership
  • Scoped validation results plus the order-specific export and delivery review

Specify the hardware and software together

A useful SONiC RFQ names the complete operating tuple rather than assuming that a switch and image are interchangeable. It should also state who owns configuration, updates, rollback, telemetry and first-line support after delivery.

  • Switch model, ASIC, interface profile, optics and breakout plan
  • SONiC distribution or image expectation, version and required features
  • Management access, gNMI or other telemetry, automation and configuration ownership
  • Upgrade, rollback, support, spares and acceptance expectations

Ask for evidence against the intended role

The acceptance request should reflect the deployment role. A leaf, spine, campus aggregation device and packet-visibility platform have different traffic, buffer, feature and operational questions. Tests are included only when agreed in the quote.

  • Intended topology role, traffic profile, oversubscription and growth basis
  • Required feature, management and telemetry observations
  • Optics, link state, configuration and recovery checks where scoped
  • Evidence format, exception handling and receiving inspection requirements

Open networking and export references

The technical sources describe SONiC and open telemetry. The Australian sources describe general export and sanctions frameworks. Neither set replaces project-specific engineering or compliance review.

SONiC quotation

Fields that prevent an ambiguous international switch order

Can any SONiC image run on any listed switch?

No such blanket assumption should be made. Confirm the exact platform, image, version, feature set, hardware support and validation boundary.

Which operational details matter most?

State configuration ownership, management access, telemetry, automation, upgrade, rollback, support and spares expectations.

Can traffic and telemetry checks be included?

They can be requested and, where accepted, defined in the quotation with conditions, evidence and pass or exception language.

Does an export quote guarantee shipment?

No. Final supply remains subject to availability, order review and applicable destination, end-user, end-use and export requirements.

SONiC RFQ

Send the platform, image, optics, operating model, destination and evidence requirements together.