Feb 06, 2026 - PicOS® Software Release Notes V4.5.0 Introduction 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. 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. Hardware Ticket ID Release Description - 4.5.6E Support FS Models N8610-32D and N8650-32OD - 4.5.5E Support FS Models N8510-24CD8D - 4.5.4E Support FS Model N8520-32D - 4.5.3E Support FS Model N9550-64D - 4.5.2E Support FS Model N9600-64OD - 4.5.1E Support FS Model N8550-24CD8D New Features Layer 2 and Layer 3 Ticket ID Release Description - 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: N9550-64D - 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. It enhances optical module management efficiency and provides strong technical support for high-performance computing (HPC) and large-scale data center networks. Feature Capabilities: Port link-up time monitoring – Records and monitors the link-up time of each port. Optical module register information reading – Supports reading detailed CMIS register data from optical modules. Repeated laser toggling (on/off) – Allows repeated laser activation/deactivation for optical module stability testing. Single-byte repeated register reading – Enables continuous single-byte read operations for debugging or validation purposes. Port alarm status monitoring (DDM) – Reads and monitors port alarm and warning information such as temperature, voltage, and optical power. Supported models: N9550-64D - 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: Lossless mode: Enables PFC and ECN, with ECN configured for WRED (Weighted Random Early Detection) and QoS policies applied. Lossy mode: Only ECN is enabled (without PFC), with ECN configured for WRED and QoS policies applied. This feature is supported on the following models: N9550-64D - 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.3E Auto Negotiation/Link Training Support the ability to display the current interface link training status. Support for the N9550-64D platform. - 4.5.3E Port Breakout Support three types of port breakout: 400G to 2*200G 400G to 4*100G 200G to 2*100G - 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 set system services web disable to modify the status of Layer 2 and Layer 3 WEB access, allowing administrators to enable or disable web access. The following switches support L2L3 WEB access, which is enabled by default: S5810-48TS-P S5810-28TS S5810-28FS S5810-48TS S5810-48FS S5860-20SQ S5860-24XB-U S5860-24MG-U S5860-24XMG S5860-48XMG-U S5860-48XMG S5860-48MG-U The following switches support L2L3 WEB access, but WEB access is disabled by default: S5870-48T6S-U S5870-48T6S S5870-48MX6BC-U S5870-48T6BC-U S5870-48T6BC Fixed Issues Layer 2 and Layer 3 Ticket ID Release Description 21166 4.5.6E [N8650-32OD] On N8650-32OD running PicOS 4.5.6E, the pica_lcmgr process could crash when an exception occurred during port speed downgrade operations. 18933 4.5.6E [MLAG] In MLAG scenarios, MAC addresses were not aged out when a LAG went down and the peer-link did not include the corresponding VLANs. 18671 4.5.6E [MLAG] In MLAG environments with large MAC tables (~30K entries), when deleting ae1 on DUT1, MAC addresses learned on ae1 were not correctly moved to the peer-link (ae10). 18594 4.5.6E [MLAG] In MLAG, the peer status shown by the show mlag link summary command incorrectly displayed as up when the peer-link was down. The expected status is unknown. 20888 4.5.6E [N8650-32OD] On N8650-32OD, error logs could be generated after the switch configuration was split and the system was rebooted. 20239 4.5.6E [N8650-32OD] On N8650-32OD, only one power module was displayed after a system reboot. 20960 4.5.6E [AN_LT] On N8610-32D, when a 200G DAC cable was connected to a 400G port and split into four lanes, auto-negotiation was incorrectly disabled. 20922 4.5.5E When 200G or 400G DAC cables were downgraded to 100G, the affected ports could fail to come up. This issue has been resolved. 19901 4.5.5E The switch could fail to load when running rc_hw.sh due to the mdio_gpio module not being enabled in the kernel. 20266 4.5.5E In ONIE mode, after selecting Uninstall OS and then performing a rescue ONIE installation, the system could fail to boot into PicOS after installation. 20860 4.5.5E When a 400G port was split into four 100G ports and forced to operate at 100G, the ports could go down and require manual LT configuration to recover. 19955 4.5.4E [System Service] Fixed an issue where executing sudo service picos stop after enabling real-time printing resulted in the error: "Error: /tmp/system/old_nslcd.conf does not exist". 20014 4.5.4E [Port Mirroring] Resolved an issue where the number of packets received on the mirrored port was incorrect after traffic transmission. 20029 4.5.4E [ACL] Fixed an issue where disabling or enabling the Spanning Tree command triggered ACL-related error logs in the BCM shell mode. 19944 4.5.4E [IPv6 RA] Fixed a failure when adding an IPv6 RA filter rule to the line card. 20187 4.5.4E [CoPP] Resolved an issue where the show command for the CoPP node was not functioning. 20208 4.5.4E [Port Security] Fixed an issue where the port-security function only allowed known unicast packets to pass, while blocking multicast, broadcast, and unknown unicast packets despite configuration. 20389 4.5.4E [NETCONF] Fixed an issue where configuring interface-related commands via NETCONF would fail. 20459 4.5.4E [PFC] Resolved a false "Only two mappings are allowed" error that occurred after deleting one mapping and adding a new one, which caused submission failure. 20516 4.5.4E [CMIS] Fixed an issue where the N8520-32D model does not support the command for modifying registers. 13698 4.5.3E [BGP] Default BGP Weight Inconsistency The configured IPv6 addresses on the connected interfaces of the two switches show different BGP weights in the routing table. The expected behavior is that both should use the same default weight value. 15507 4.5.3E [MLAG + Anycast GW] After MLAG status is full, changing a VLAN interface from the default VRF to VRF1 and configuring IPv6/Anycast IPv6 addresses results in a neighbor table synchronization failure between MLAG peers. 18960 4.5.3E [N8550-24CD8D/N9550-64D] The ACL matching condition is mismatched - packets without TCP/UDP headers are mistakenly matched against the rule source-port 0..0. A large number of sequential ACL rules were configured. Among them, filter f1 sequence 4000 specifies ICMP type 0 and ICMP code 57. When ICMP packets with type 0 and code 57 (which do not contain TCP/UDP headers) are sent, they are incorrectly matched by sequence 1300, which defines the condition source-port 0..0. 13587 4.5.3E [FRR: MLAG] Fixed an issue where, after MLAG reached the full state, deleting a static MAC address on one peer caused the corresponding dynamic MAC address on the other peer to fail to synchronize. 18922 4.5.3E [N9550-64D 4.5.3E] Fixed an issue where, after inserting and activating a 400G module, changing the port rate to 100G did not update the port status correctly - the port remained displayed as 400G up. 17889 4.5.3E [FRR: OSPF6] The ifindex value of the interface that introduces the route is inconsistent before and after the port UP/DOWN operation.After configuring static OSPF6 routes on DUT1, the ifindex value associated with the static routes changes when the interface is toggled (UP/DOWN), resulting in an inconsistency compared to the initial state. 16367 4.5.3E [FRR] The Hostname Display is Inconsistent across Different Platforms When running in FRR mode, some switches display hostname PICOS in the show running-config output, while others do not. 18820 4.5.3E [MLAG] The Partner Port Number information displayed for the LACP port under MLAG is incorrect. 18911 4.5.3E [N9550-64D | 4.5.3E] The QDD-SR4-2x100G module could not be recognized on the Tomahawk4 platform. 19706 4.5.3E [Tomahawk4] When a split port is configured as 200G, the headroom size is calculated based on the 10G port configuration, resulting in incorrect headroom allocation. 19743 4.5.3E [MLAG Trident4] If VLAN 1 is included in the peer-link VLAN and additional links exist between the two MLAG devices other than the peer-link, MLAG synchronization packets may loop between the devices. 18217 4.5.3E [S6860-24CD8D] When MLAG and L3 Anycast are configured simultaneously, ARP entries cannot be learned properly. 18197 4.5.3E [S6860-24CD8D | MLAG] Traffic received from the peer-link should be dropped on the peer-link port in an MLAG environment. 17752 4.5.3E [Trident4 | N8550-24CD8D | MLAG Peer-Gateway] When MLAG Peer-Gateway is configured, the downstream device can obtain ARP and ping successfully, but SSH connections fail. 17233 4.5.3E [N8550-24CD8D | MLAG] The MLAG downlink LACP port fails to come up during negotiation. 19648 4.5.3E [MLAG] In an MLAG cascading environment, some packets are flooded through the MLAG peer-link after adding a new physical port to the peer-link while one MLAG member port is down. 18219 4.5.3E [N9600-64OD / S6860-24CD8D | MLAG + DHCP Relay + VRRP] After all DHCP IP addresses are successfully learned, sending a DHCP Release packet to delete one IP fails immediately and takes about two minutes to complete. 19380 4.5.3E [MTU | Tomahawk5 / Tomahawk4 / Trident4] Layer 3 MTU configuration does not take effect on Tomahawk5, Tomahawk4, and Trident4 platforms. 20394 4.5.3E [Tomahawk4] After splitting all ports, the DDM information of the last few ports with optical modules inserted is not displayed. 18564 4.5.0M2 [MLAG] After configuring MLAG, the run show mlag link command always shows the link state as IDLE. This issue has been fixed. 18446 4.5.0M2 [MLAG/MLAG+EVPN] After the MLAG peer restarts or reboots, the MLAG domain status stays at CONNECTING, while the peer shows ESTABLISHED. The issue is caused by the MLAG socket using the loopback address instead of the configured MLAG IP. This issue has been fixed. 15919 4.5.0M2 [MLAG] MLAG occasionally fails to reach FULL state, with error log: local0.err : [SIF]Socket 99 connect is in progress. This issue has been fixed. 17340 4.5.0M2 [N8560-64C] Port LED stays off even when the port is operational with an optical module installed. 17378 4.5.0E [DOT1X] Setting the session timeout to 0 on the NAS and a non-zero session timeout on the NAC server causes a crash during 802.1X re-authentication. The bug is fixed in 4.5.0E. 17760 4.5.0M2 [SNMP] LLDP Neighbor Information Retrieval Issue When the number of LLDP neighbors exceeded five, SNMP failed to retrieve LLDP neighbor details. This issue has been fixed. 17386 4.5.0M2 [LLDP] SNMP Notification Issue after Interface Reconfiguration After enabling an interface by using command set interface gigabit-ethernet xx disable true and then disabling it by using command delete interface gigabit-ethernet xx disable, LLDP might not notify SNMP. This issue has been resolved. 17531 4.5.0M2 [DHCP Server] Address Assignment Failure with Excessive Address Pools In a direct connection scenario, configuring too many address pools caused the configuration file size to exceed 1024 characters, preventing the DHCP server from assigning IP addresses. This has been fixed. 17481 4.5.0M2 [N9550-32D] Port LED Issue in Breakout Mode When enabling breakout mode for 2×200G, the port LEDs did not illuminate. This issue has been addressed. 17544 4.5.0M2 [CLI] No Output for Interface Command on AS9716-32D On the AS9716-32D platform, executing the command run show interface gigabit-ethernet xe-1/1/xx and pressing Enter produced no output. This issue has been fixed. 17556 4.5.0M2 [AS4610/N3024/N3048] System Crash when Handling Large Files Copying or creating large files locally caused a core.bcmINTR error, leading to the pica_lcmgr process crashing. The kernel didn't report any errors, but PicOS restarted after some time. This issue has been fixed. 17330 4.5.0M2 [N5850-48S6Q] High CPU Usage and Memory Leak Due to FPM Packet Handling When receiving unknown packets, FPM discarded them but did not close the socket, leading to memory leaks and 100% CPU usage. This issue has been resolved. 17647 4.5.0M2 [ACL - BCM] VRRP Virtual MAC Incorrectly Installed in ACL In L2/L3 configurations, the VRRP virtual MAC (00:00:5e) was added to ACL even when VRRP was not configured, causing ping traffic destined for the VRRP MAC to be blocked. This issue has been fixed. 17366 4.5.0M2 [SIF] VLAN Removal Issue Affecting Kernel Configuration If a trunk port was configured with a native VLAN that was also a VLAN member, removing the native VLAN via CLI caused the kernel to incorrectly delete the VLAN, leading to VLAN anomalies. This issue has been fixed. 18806 4.5.0M2 [N8550-32C] Cannot Correctly Read the SN (Serial Number) of the Power Module When you execute the show system serial-number command on N8550-32C, the RPSU 1 Serial Number information cannot be displayed correctly. This issue has been fixed. 19136 4.5.0M2 [MLAG N9550-32D] The MAC Learning Issue after the Counting Number Exceeds 8K In the MLAG scenario of N9550-32D, due to the flaw in the SDK's MAC address counting mechanism, some MAC addresses are counted repeatedly. Even when the actual number of MAC entries has not reached the maximum capacity limit, the switch stops learning new MAC addresses. This issue has been fixed. Known Limitations Ticket ID Release Description - 4.5.6E Functional Limitations PicOS 4.5.6E does not support the following features: DCBX, Private VLAN, MAC-based VLAN, QINQ, IPv6 ND snooping, IPv6 ND Inspection, IGMP Snooping, MLD, MLD snooping, Multicast VPN, PIM(IPv6), PIM DM, PIM snooping, Multicast over VXLAN, BGP graceful-restart, Rate Limit, Storm Control, NAC, VXLAN, BFD for LACP, BFD for VRRP+, BFD for PBR, BFD-ISIS, BFD for MPLS, BFD for PIM-SM, MLAG with DHCP relay, MLAG with IGMP snooping, MLAG+VXLAN, ACL-based Traffic Policer, ACL-based QoS, Port Security, PTP, MPLS, IPv6 Source Guard, PoE, and OVS. - 4.5.5E Functional Limitations PicOS 4.5.5E does not support the following features: GRPC, DCBX, Private VLAN, MAC-based VLAN, QINQ, IPv6 ND snooping, IPv6 ND Inspection, IPv6 NDP, IGMP Snooping, MLD, MLD snooping, Multicast VPN, PIM, PIM DM, PIM snooping, Multicast over VXLAN, BGP graceful-restart, Rate limit, Storm Control, NAC, GRE, VXLAN, MLAG with DHCP Snooping, MLAG with DHCP relay, MLAG with IGMP snooping, ACL-based Traffic Policer, ACL-based QoS, Port Security, PTP, MPLS, IPv6 Source Guard, and PoE. - 4.5.4E Functional Limitations PicOS 4.5.4E does not support the following features: Differentiated Flow Scheduling for Elephant and Mice Flows, DCBX, IGMP snooping, VXLAN, QINQ, Private VLAN, Voice VLAN, MAC-based VLAN, Sflow, STM, NAC, IPv6 ND snooping, IPv6 ND Inspection, IPv4 Source Guard, IPv6 Source Guard, PIM(IPv6), PIM DM, PIM snooping, GVRP, MVRP, ZTP, RIP timer, RIP passive-interface, ERPSv1, ERPSv2, ISIS, DHCPv6 Guard, Route Map, NTP, PTP, DNS, Local Loopback, BPDU Root Guard, BPDU TCN-Guard, BPDU-Guard, DHCP server and DHCP client, IPv6 DHCP Relay, Unidirectional Link Detection (UDLD), and Loopback Detection. - 4.5.3E Functional Limitations PicOS 4.5.3E does not support the following features: GRPC, DCBX, Private VLAN, MAC-based VLAN, QINQ, IPv6 ND snooping, IPv6 ND Inspection, IPv6 NDP, IGMP Snooping, PIM, PIM DM, PIM snooping, Multicast over VXLAN, BGP graceful-restart, Rate limit, Storm Control, NAC, GRE, VXLAN, MLAG with DHCP Snooping, DHCP relay, IGMP snooping, ACL-based Traffic Policer, ACL-based QoS, Port Security, PTP, MPLS, IPv6 Source Guard, and PoE. 18171 4.5.2E [N9600-64OD] Some sub-interfaces cannot come up in 8×50G mode when using the OSFP-SR8-800G module. 18400 4.5.2E [N9600-64OD] The port light remains illuminated after the module is removed in port splitting mode. 18091 4.5.2E [N9600-64OD] Undersized packets are not counted in the interface's 'Undersize Packets' statistics. 18504 4.5.2E [N9600-64OD] The BMC light remains red after a successful system startup.PICOS does not control the BMC light. The light changes from flashing green to solid red. 18501 4.5.2E [N9600-64OD] Front Panel Ports 65 and 66 Not Supported The two SFP front panel ports (65 and 66) are not adapted and are not supported in 4.5.2E. - 4.5.2E [N9600-64OD] Packets smaller than 295 bytes will not reach full line rate due to hardware limitations. - 4.5.2E [N9600-64OD] This platform uses software-based MAC address learning, resulting in a slower learning rate compared to hardware-based platforms. - 4.5.0M2 PICOS 4.5.0M does not support OSPF Multi-Instance. - 4.5.0M2 PICOS 4.5.0M does not support telnet server. - 4.5.0E 4.5.0M2 Performance Limitation For certain PICOS switches, the pica_snmp process may consume more resources under specific application scenarios, degrading the system responsiveness. For details, see Northbound Performance to Be Improved. Known Issues Ticket ID Release Description 20912 4.5.6E [N8610-32D] Switch may crash when committing a large number of ACL rules in a short period Description When more than 700 ACL rules are committed rapidly (for example, via scripts), the ACL log may refresh continuously, which can eventually cause the switch to crash. Impact This issue may occur on all platforms when a large number of ACL rules are committed multiple times within a short period. Workaround Avoid committing a large number of ACL rules in rapid succession. It is recommended to batch ACL changes and allow sufficient intervals between commits. Fix Version This issue is planned to be fixed in PicOS 4.9.0E. 19142 4.5.6E [Automation / CLI] Error message displayed when deleting a LAG interface after repeated rollback operations Description After creating a LAG interface (for example, ae1), adding member ports, and executing rollback 1 multiple times, deleting the LAG interface may succeed at the command level but fail during commit, with an incorrect error message displayed. Impact This issue does not affect normal functionality. However, the error message is misleading. When a LAG interface is still referenced by other configurations, the system should indicate that the interface is in use, rather than reporting that it does not exist. Workaround Before deleting a LAG interface, ensure that all related configurations are removed. 21013 4.5.5E On the N8510-24CD8D platform, the following QSFP modules may fail to establish a link. The module type reported by the system does not match the expected module model name: QSFP-BX40-100G QSFP-BX10-100G As a result, the port remains in a disconnected state. 19926 4.5.5E The ovs-vswitchd process (OVS core daemon) may fail to configure the port statistics debug counter type under certain conditions. 20036 4.5.5E In OVS mode, a 200G port incorrectly indicates support for the 10G rate. Impact: The rate capability display is inaccurate. This issue does not affect actual port functionality or traffic forwarding. 21141 4.5.5E On the N8510-24CD8D (version 4.5.5E), when ports 3, 4, or 5 are used to send RoCE traffic in an 8-port configuration, the output port statistics for Queue 3 do not display packet reception information. When the traffic source ports are changed to ports 1, 6, or 7 and traffic is sent to port 8, the output port statistics are displayed correctly. 19940 4.5.4E [OVS] In OVS mode without traffic capture, port statistics display a series of numbers. 19926 4.5.4E [Icmgr_ovs] The ovs-vswitchd daemon failed to set the "port statistics debug counter type". 20027 4.5.4E [OVS] Adding a port in OVS mode results in an error. 20037 4.5.4E [STM] A "commit fail" error occurs when attempting to remove the previously committed configuration command set interface stm firewall-table egress 33. 19961 4.5.4E [CoPP/NDP] When sending unlabeled NDP traffic with incorrect headers (5 packets each for NS/NA/RS/RA, totaling 20 packets), the CoPP NDP-class statistics show Input Packets=0, which is inconsistent with expectations. 17445 4.5.4E [VLAN Interface] The show l3-interface vlan-interfacecommand does not display counters, while physical port counters function correctly. 19304 4.5.4E [PFC Watchdog] The packet loss count is inaccurate when the TD4 watchdog action is triggered to drop packets. 16594 4.5.4E [IGMP Snooping] IGMP snooping does not function on the N8520-32D model. 17395 4.5.4E [Port Statistics] Packet loss statistics are not displayed in port statistics when tagged traffic with a non-matching VLAN ID is sent to the port. 17765 4.5.4E [Neighbor Discovery] The local side does not receive neighbor information when a static neighbor is configured on the peer. 20564 4.5.4E [Hardware Compatibility] The N8520-32D hardware is incompatible with the optical module QSFP-100G-ZR. 16172 4.5.3E [MLAG + DHCP Snooping + VRRP] DHCP snooping bindings sometimes fail to synchronize to the peer switch. 18914 4.5.3E [OVS] Tomahawk5 / Tomahawk4 / Trident4 platforms do not support snake-like traffic streaming in OVS mode. 17503 4.5.3E [N9550-64D] Multicast traffic fails to forward according to the IGMP snooping table. 18947 4.5.3E [N9550-64D] When the aggregate port (ae1) joins a multicast group, traffic is transmitted, but the corresponding member ports do not receive multicast packets. 14732 4.5.3E [EVPN MH Aliasing] Packets cannot be redirected to the ES peer switch after the ESI port goes down. 18827 4.5.3E [MLAG IGMP Snooping] After Ixia sends Query packets to DUT1 and DUT3 responds with Report packets to establish IGMP snooping entries, Ixia again sends multicast packets to DUT1, but DUT3’s Ixia port fails to receive them. 19490 4.5.3E [STM CLI] STM route configurations cannot be deleted or modified. 19613 4.5.3E [Tomahawk4] After changing the route parameter, the system prompts for a reboot to take effect, but the change actually takes effect immediately without reboot. 19642 4.5.3E [Tomahawk4 | STM] The configured STM MAC table values did not take effect after restart; the maximum MAC value in the STM table remained unchanged. 19644 4.5.3E [Tomahawk4 | STM] The number of IPv6 route entries exceeds the maximum supported limit. 19699 4.5.3E [STM] The system allows adding static routes that exceed the maximum supported limit. 19709 4.5.3E [MLAG + VRRP + DHCP Snooping + Relay] DUT4 sends an asynchronous RP packet; DUT1 learns the MAC address and forwards host information, but DUT2 fails to learn it. 17882 4.5.3E [Tomahawk4 | N9550-64D] When sending TCP packets with incrementing source MAC addresses, LAG/LACP fails to perform load sharing. 17369 4.5.3E [N9550-64D] The 400G breakout mode (4×100G) cannot be used on 9716; all ports remain down even when connected to itself or to other DUTs such as N9550-64D. 17091 4.5.3E [N9550-64D] When you use a 200G module on a 400G port and break it out into 4×50G, only two subports come up. 17967 4.5.3E [ECMP] Error messages should not contain parentheses or square brackets in commit failed outputs. 16658 4.5.3E [ECMP Route] Configuring more ECMP groups than the system limit may cause a crash. 20395 4.5.3E [Tomahawk5] After splitting an 800G port, it cannot come online unless all breakout subports are equipped with optical modules.

PicOS® Software Release Number

Feb 06, 2026 - PicOS® Software Release Number Software Release Numbers The format of PicOS® release version number is x.y.zF. Table 1 shows the description of each letter. Table 1. Description of Release Version Number Letter Description x Major release version number Updated in the following cases: • Major code changes: such as FRR support. • New significant features: such as Linux kernel upgrade support. y Minor release version number Updated in the following cases: • New feature sets, sub-features, or feature enhancements • New hardware platforms, including new ASICs or chipsets z Maintenance release version number The version marked with E indicates that it contains new features or new hardware platform. The number is updated in the following cases: • Security updates. • New hardware platforms for existing ASICs or chipsets, or released in separate branches. The version marked with M indicates that it is in the maintenance phase. The number is updated in the following cases: • Bug fixes and updates. F Release version type E: introduces new features or supports new hardware platform, which is available for early sales and certain experimental bureaus. M: regularly releases patches to fix issues, achieving a high level of stability. Null (No letter): the hotfix version before GA version is released.

PicOS® Configuration Guide V4.5

Feb 06, 2026 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

PicOS® CLI Reference Guide V4.5

Feb 06, 2026 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

Edgecore & Dell & Delta Switches PicOS® 4.6.0E Software

Feb 05, 2026 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

Edgecore AS4625 Switches PicOS® 4.6.0E Software

Feb 05, 2026 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

Edgecore AS4610 Switches PicOS® 4.6.0E Software

Feb 05, 2026 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

Feb 05, 2026 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

Feb 05, 2026 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

Feb 05, 2026 - For details, please click the attachment icon below to view or download for a good reading experience or resources.