Cato Networks may find it necessary to discontinue specific Cato Socket hardware models and refresh them with newer, up-to-date hardware. This occurs for a number of reasons, including hardware lifecycle maturity, technology innovation, or the introduction of platforms with expanded capabilities.
While ownership of Cato Socket hardware transfers upon its delivery, the Socket operates as an integral component of Cato’s subscription-based service. As part of that subscription, Cato manages the supported hardware lifecycle, including hardware refreshes and end-of-support (EOS) processes. This policy is intended to help customers plan for and manage hardware refresh activities in alignment with Cato’s supported service lifecycle.
When Cato Socket hardware approaches its refresh or end-of-support (EOS) stage, Cato is committed to communicating all important milestones throughout the process. These communications include the initial Refresh Start announcement, the End-of-Support (EOS) date, and other key information relevant to Cato Socket hardware, including guidelines to ensure a smooth transition for our customers.
Any hardware requiring a refresh will typically be identified by Cato at least 90 daysprior to the Refresh Start Date. The refresh process is usually initiated during the subscription renewal, and the Refresh Start Date generally corresponds with the new subscription renewal date.
Once hardware models move into the refresh cycle, they are removed from all new deployments/deliveries. End-of-Support is usually communicated several years after their End-of-Sale date, in line with industry standard.
Payments: Refreshed Sockets are provided at no additional charge, including shipping, in connection with the customer’s existing subscription. However, Cato’s subscription fees may be updated over time in accordance with market conditions.
Cato recommends completing the refresh to the newly provided hardware as soon as possible to maintain service continuity and adhere to best practices. Cato will continue to support the existing hardware throughout the refresh window (at least 12 months), even if the customer has not yet replaced it with the provided new hardware. However, once the EOS date is reached, support for the existing hardware will cease. After that date,the affected customer site will no longer be supported, and service disruption may occur. Additionally, if the existing hardware becomes defective during the refresh window, Cato will not ship an old Socket model to replace it, and the customer will need to use the new hardware.
Cato’s hardware refresh approach ensures functional continuity when migrating to new hardware. While the new hardware may deliver higher performance and scale, core features and behaviors stay consistent. Along with this seamless service continuity, the refreshed models also typically deliver higher compute power, improved efficiency, and up-to-date hardware capabilities.
Although legacy Cato Socket hardware may continue to function after the EOS date, the following practices and limitations apply:
-
Cato will not proactively disconnect end-of-support Sockets, however, continued operation is not guaranteed.
-
Cato cannot guarantee that legacy hardware will remain compatible with, or able to connect to, the Cato platform as the platform evolves.
-
Cato Technical Support will no longer provide troubleshooting, replacement, or repair for legacy hardware.
-
Cato may no longer provide software updates or patches for legacy hardware.
-
New features, improvements, and security patches—including those addressing critical CVEs—may not be compatible with legacy hardware or its software.
Note: Cato Cloud services (e.g. antimalware) are not impacted by end-of-support for a Socket.
-
Continuing to run Sockets past their EOS date is a security risk.
Refresh Start Announcement:
Issued at least 90 days prior to the Refresh Start Date, typically aligned with subscription renewal.
Refresh Window:
A minimum 12-month period following the Refresh Start Date during which customers are expected to replace affected hardware. The EOS date will occur no earlier than 12 months after the Refresh Start Date.
End-of-Support (EOS) Date:
The last date on which a Socket model is actively supported by Cato. After this date, the hardware is considered unsupported. Each Socket model has a designated EOS date.
End-of-Support (EOS) Announcement:
Typically communicated approximately four (4) years before the EOS date and published on a per-model basis.
Longevity:
Cato generally supports a Socket model for at least seven (7) years—and often up to ten (10) years—from the start of service to the EOS date. While not a formal guarantee, Cato typically announces EOS approximately four (4) years in advance.
Customer Responsibilities:
-
Physically replacing the Socket at the customer’s premises.
Cato Responsibilities:
-
Initiating and supporting the refresh process when a Socket reaches EOS or is scheduled for replacement.
-
Covering shipping costs for replacement Sockets.
-
Hardware Sockets that are declared EOS will no longer be offered for sale and are typically withdrawn from sale well in advance of any refresh or end-of-support activities. Following an EOS announcement, all new orders will include only active Socket models (those not listed as EOS).
-
Replacement hardware provided under RMA will always be fulfilled with the latest active Socket model—never with a model that has reached EOS.
0 comments
Article is closed for comments.