Release Notes for PICOS 4.5
These notes summarize PICOS 4.5 new features, new hardware, known bugs, and bug fixes. Best practices recommend that you read all the content before upgrading to this release. For more detailed feature information, refer to the configuration guides.
Released Versions
PICOS 4.5 provides two separate software tracks for different chip platforms. You can view the information of corresponding versions as needed.
Versions for RTL Chip Platforms
PICOS 4.5.0E-EC2 has been released as an ESS (Early Sales Support) version for new platforms S3240-8P, S3240-24P, delivering a high-density wireless access solution for SME scenarios. It supports high-power PoE+, 10G uplinks, and multi-Gigabit access, addressing the gap in multi-rate access solutions for PICOS switches in SME deployments.
PICOS 4.5.1E-EC2 has been released as an ESS (Early Sales Support) version for new platforms S3260-10S and S3260-8MU, enabling a high-density wireless access solution with 10G uplinks and Multi-Gig access, addressing the gap in multi-rate access solutions for PICOS switches in SME deployments. The S3260-8MU PoE delivers up to 90W per port, meeting the power demands of high-load devices.
Based on Version:
Optimized and iterated based on PICOS V4.5.0E
Versions for Other Platforms
PICOS 4.5.0E has been released as an ESS (Early Sales Support) stable version, aimed at supporting specific customer deployments and early adoption scenarios. This release provides early access to new features and enhancements tailored for targeted use cases. It serves as an intermediary step between internal testing and the General Availability (GA) release, enabling customers to explore and deploy features in controlled environments.
PICOS 4.5.1E version is an evaluation release specifically designed for the N8550-24CD8D platform. This release focuses on providing a foundational feature set but comes with certain limitations in functionality and usage. Please note that the current version supports only core features of the N8550-24CD8D platform, with some advanced capabilities not yet fully implemented or optimized.
PICOS 4.5.2E released as an ESS version for new platform N9600-64OD.
PICOS 4.5.0M2 is a GA release that brings enhanced stability and performance improvements. This version supports all platforms except S3410 series, S3270 series, N5860-48S6Q, N8550-24CD8D, and N9600-64OD switches, ensuring broader compatibility and reliability for network deployments.
PICOS 4.5.3E released as an ESS version for new platform N9550-64D. This release provides a foundational feature set but comes with certain limitations in functionality and usage.
PICOS 4.5.4E released as an ESS version for new platform N8520-32D.
PICOS 4.5.5E released as an ESS version for new platform N8510-24CD8D.
PICOS 4.5.6E released as an ESS version for new platforms N8610-32D and N8650-32OD.
PICOS 4.5.3.2 released as an iterative version for platforms N9550-64D, N8550-24CD8D, and N9600-64OD.
This version primarily introduces gRPC support, and extends multiple features to Trident4 and Tomahawk5-based platforms, improving overall manageability and operational visibility.
Key improvements in this release include:
Management & Operations Enhancements
Enhanced network visibility through real-time telemetry support for PFC, ECN, and DDM, enabling more efficient monitoring and troubleshooting.Platform Feature Alignment
For Trident4-based N8550-24CD8D and Tomahawk5-based N9600-64OD, this ESS release adds several functional capabilities that were already supported on Tomahawk4-based N9550-64D in the PICOS 4.5.3E release, achieving better feature consistency across platforms.
PICOS 4.5.5.1 released as an iterative version for platform N8510-24CD8D.
PICOS 4.5.7E released as an ESS version for new platforms AS9737-32DB and AIS800-32O.
PICOS 4.5.8E released as an ESS version for new platform N8610-64DB. This release provides a foundational feature set but comes with certain limitations in functionality and usage.
PICOS 4.5.3.3 is based on 4.5.3.2 and introduces updates to hardware platform names to align with the updated product naming convention. This release adds support for the new hardware platform name N8650-64OD and updates the existing platform name N9600-64OD to N8650-64OD.
Apart from the hardware platform name update, there are no changes to software features, CLI behavior, or compatibility compared with 4.5.3.2. This release is fully backward compatible, and upgrades can be performed without operational impact.
Previous Model Name | Updated Model Name |
|---|---|
N9600-64OD | N8650-64OD |
Supported Platforms and Features
Supported Platforms
Release | Supported Platforms |
|---|---|
4.5.1E-EC2 | S3260-10S, S3260-8MU |
4.5.0E-EC2 | S3240-8P, S3240-24P |
4.5.7E | AS9737-32DB, AIS800-32O |
4.5.6E | N8610-32D, N8650-32OD |
4.5.5E | N8510-24CD8D |
4.5.4E | N8520-32D |
4.5.3.2 | N9550-64D, N8550-24CD8D, N9600-64OD |
4.5.3E | N9550-64D |
4.5.2E | N9600-64OD |
4.5.1E | N8550-24CD8D |
Supported Features
To view supported features of different platforms and versions, see PICOS Supported Features.
New Features
Layer 2 and Layer 3
Ticket ID | Release | Description |
|---|---|---|
- | 4.5.3.2 | DDM Telemetry PICOS now supports retrieving optical module Digital Diagnostic Monitoring (DDM) information through both the CLI and the gNMI northbound interface. Key features include:
This feature is supported on the following platforms:
|
- | 4.5.3.2 | PFC/ECN Telemetry PICOS supports PFC and ECN telemetry monitoring via the gRPC northbound interface, enabling enhanced visibility into congestion control behavior on the switch. The following metrics can be monitored:
This feature is supported on the following platforms:
|
- | 4.5.3.2 | MOD Telemetry PICOS supports MOD telemetry monitoring via the gRPC northbound interface, providing detailed visibility into module operations. The key metrics monitored include 13-dst-lookup-miss, 13-header-err, and 13-ttl-err. This feature is supported on the following platforms:
|
- | 4.5.3.2 | New Features by N8550-24CD8D and N9600-64OD This section summarizes the major new features introduced for specific platforms in this release. Trident4 – N8550-24CD8D Version upgrade: 4.5.1.5 → 4.5.3.2 The following key features are newly supported on the N8550-24CD8D platform:
Tomahawk5 – N9600-64OD Version upgrade: 4.5.2E → 4.5.3.2 The following key features are newly supported on the N9600-64OD platform:
|
- | 4.5.3E | MOD CLI A technology specifically designed to monitor packet loss during internal device forwarding of messages. Once MOD detects packet loss inside the device, it will immediately collect the time of packet loss, the reason for packet loss, and the characteristics of discarded messages, and report them to the remote collector so that administrators can timely understand the packet loss situation inside the device. Currently, this feature supports three types of packet drop monitoring through CLI configuration: ingress-l3-dst-lookup-miss, ingress-l3-header-err, and ingress-l3-ttl-err. |
- | 4.5.3E | Differentiated Flow Scheduling for Elephant and Mice Flows Network traffic can generally be categorized into high-volume (elephant) and low-volume (mice) flows based on the amount of data transmitted within a given time period. This feature is supported on the following model: |
- | 4.5.3E | CMIS Protocol Optical Module Information Reading This feature introduces comprehensive CMIS protocol–based monitoring and diagnostic capabilities for 400G optical modules, enabling precise control and visibility into module performance and link stability. Feature Capabilities:
Supported models:
|
- | 4.5.3E | ROCE EasyDeploy The switch collaborates with servers to enable one-click RoCE deployment, supporting both lossless and lossy modes (default: lossless), with the ability to switch between modes:
This feature is supported on the following models: |
- | 4.5.0E | IPv6 ND Inspection IPv6 Neighbor Discovery (ND) Inspection is a security feature designed to enhance the protection of IPv6 networks by managing and validating Neighbor Discovery Protocol (NDP) messages, which are essential for the proper operation of IPv6 communication. Please have the details by reference document IPv6 Neighbor Discovery Inspection. |
- | 4.5.0E | IPv6 ND Snooping IPv6 Neighbor Discovery (ND) Snooping is a security feature that safeguards IPv6 networks to prevent various types of attacks. It functions similarly to ARP (Address Resolution Protocol) Snooping in IPv4 networks. Please have the details by reference document IPv6 Neighbor Discovery Snooping. |
- | 4.5.0E | MPLS MPLS (Multiprotocol Label Switching) operates between the link layer and the network layer in the TCP/IP protocol stack. It offers connectivity services to the IP layer while leveraging services from the link layer. Unlike traditional IP forwarding, MPLS uses label switching to direct traffic through the network. Please have the details by reference document MPLS Configuration. |
- | 4.5.0E | PIM BSR (Bootstrap Router) Dynamic RP allows multiple PIM devices within a PIM domain to be configured as C-RPs (Candidate RPs). Among these C-RPs, an RP is determined through an election process. The BSR aggregates information from all C-RPs in the network into an RP Set using Bootstrap messages and distributes it to all PIM devices. Each PIM device uses the RP Set to calculate and compare based on consistent rules, ultimately selecting an RP from the available C-RPs. Please have the details by reference document PIM Configuration Guide. |
- | 4.5.0E | Ingress Buffer Supports ingress buffer management, including guaranteed/shared/headroom management. Please have the details by reference document Configuring PFC Buffer. |
- | 4.5.0E | PFC Watchdog Manual Control The PFC Watchdog feature detects and resolves PFC (Priority Flow Control) deadlocks. Recovery methods include both automatic and manual recovery, allowing users to choose the appropriate approach for resolving deadlock scenarios. Please have the details by reference document Configuring PFC Watchdog. |
- | 4.5.0E | PFC Deadlock Prevention To avoid PFC deadlock issues, the DSCP value and corresponding Dot1p priority of the message can be modified so that the modified message can be forwarded using the new DSCP value in the new Dot1p priority queue, avoiding messages with the same DSCP value from remaining in PFC deadlock state. Please have the details by reference document Configuring PFC Deadlock Prevention. |
- | 4.5.0E | Easy ECN Explicit Congestion Notification (ECN) is a congestion notification mechanism operating at the IP and transport layers, serving as an extension to the TCP/IP protocol. With Easy ECN, users can enable WRED (Weighted Random Early Detection) policies, configure WRED thresholds, and set the maximum packet loss probability to manage network congestion more effectively. Please have the details by reference document Configuring Easy ECN. |
- | 4.5.0E | DLB (Dynamic Load Balance) DLB breaks through the limitations of traditional static hash mechanisms by introducing timestamp and real-time load measurement factors (port bandwidth load, queue size) to optimize load balancing in both time and bandwidth space dimensions, providing a dynamic and intelligent hash mechanism. Please have the details by reference document Configuring Dynamic Load Balancing. |
- | 4.5.0E | Standby IP Address In cases where the management port cannot connect to the DHCP server and no static IP has been set through CLI during the switch's startup, it will default to using the secondary management IP address 192.168.1.1. This IP address serves as a backup, allowing management of the device even if DHCP services are unavailable. It is primarily used when the management port is directly connected to a PC, ensuring uninterrupted device management via this IP address. Please have the details by reference document Default Settings for Out-of-band Management Interface. |
- | 4.5.0E | Perpetual PoE Perpetual PoE (also known as hot-start uninterruptible power supply or permanent PoE) refers to the ability of Power Sourcing Equipment (PSE) to continue providing power during a system restart. This includes restarts initiated through CLI commands such as "request system reboot" or by rebooting under the Linux shell. Additionally, it supports uninterrupted power during system upgrades, including upgrades triggered via CLI or Linux-based upgrade methods. This feature ensures that PoE-powered devices remain operational even when the system is restarting or undergoing an upgrade. Please have the details by reference document Configuring Perpetual PoE. |
- | 4.5.0E | PFC/ECN GRPC monitoring PFC and ECN, in conjunction with gRPC, can provide PFC pause frame counts, PFC deadlock monitoring and ECN-marked packet counts for statistical queries. Please have the details by reference document PFC and ECN Statistical Reporting through gRPC. |
Feature Enhancement
Ticket ID | Release | Description |
|---|---|---|
- | 4.5.5.1 | gRPC Feature Enablement and Optimization The gRPC functionality has been enabled and optimized in this release to improve system usability and performance on N8510-24CD8D. |
- | 4.5.3.2 | CMIS Protocol Optical Module Information Reading For 400G switch products, PICOS now supports monitoring, reading, and writing optical module information via the CMIS protocol, providing enhanced capabilities for high-performance computing cluster networks and meeting future HPC infrastructure requirements. Key enhancements include:
Supported Models:
|
- | 4.5.3.2 | MOD CLI PICOS introduces MOD CLI, a feature designed to monitor packet loss within the device’s internal forwarding plane. When MOD detects packet loss, it immediately collects the timestamp, reason for loss, and characteristics of discarded packets, and reports this information to a remote collector, enabling administrators to quickly understand and respond to internal packet loss events. Supported Drop Packet Scenarios via CLI:
Supported Models:
Note: The Tomahawk4 N9550-64D model already supports this feature since version 4.5.3E. |
- | 4.5.3.2 | gRPC Optimization PICOS has optimized gRPC performance to address high CPU utilization issues observed after gRPC is enabled. These improvements enhance system stability and allow more efficient monitoring and management via the gRPC northbound interface. Supported Models:
|
- | 4.5.3E | Auto Negotiation/Link Training
|
- | 4.5.3E | Port Breakout Support three types of port breakout:
|
- | 4.5.0E | DHCP Server Enhancement In versions prior to 4.5.0E, clients were unable to obtain an address in a DHCP relay scenario. However, starting from version 4.5.0E, this issue has been resolved, and the system now fully supports DHCP address assignment in relay scenarios. |
- | 4.5.0E | DHCP ZTP After enabling the DHCP server with PicOS, address pools can be configured to allocate IP addresses to clients, along with additional network information such as gateway, DNS server addresses, log server addresses, TFTP server addresses, boot file names, and other options. These configurations are applied and synchronized with the clients as addresses are allocated. Please have the details by reference document Zero Touch Provisioning (ZTP). |
- | 4.5.0E | 400G Port Splitting The N9550-32D/AS9716-32D switches support the capability to split a 400G port into 2 * 200G and split to 4 * 100G ports, providing flexible bandwidth allocation for diverse network needs. Please have the details by reference document Configuring Port Breakout and Merge. |
- | 4.5.0E | PBR ECMP PBR (Policy-Based Routing) action supports not only specifying a next-hop router or modifying DSCP values, but also enables the use of nexthop-group for ECMP (Equal-Cost Multi-Path) routing, allowing for more advanced and efficient traffic distribution across multiple paths. Please have the details by reference document Policy-Based Routing (PBR). |
L2L3 WEB
Ticket ID | Release | Description |
|---|---|---|
- | 4.5.0E | L2L3 WEB Access Control Support is provided for using the command The following switches support L2L3 WEB access, which is enabled by default:
The following switches support L2L3 WEB access, but WEB access is disabled by default:
|
Fixed Issues
Layer 2 and Layer 3
Ticket ID | Release |
|---|