Support FS model N8560-32CModels S5860-24MG-U, S5860-24XMG, S5860-48XMG-U and S5860-48XMG

PICOS 4.4.3.8 only 13 release for FS model N8560-32C.
N8560-32C has 32x100G QSFP28 ports.

Support FS Models S5860-20SQ and S5860-24XB-U

PICOS 4.4.3.3 release for FS models S5860-20SQ and S5860-24XB-U.

S5860-20SQ has 20x10G SFP+ ports, 4x25G SFP28 ports and 2x40G QSFP+ ports.
S5860-24BX-U has 24x10G copper ports, 4x10G SFP+ ports and 4x25G SFP28 models S5860-24MG-U, S5860-24XMG, S5860-48XMG-U and S5860-48XMG.

S5860-24MG-U has 24x5G copper ports, 4x25G SFP28 ports.

S5860-24XMG has 24x10G copper ports, 4x10G SFP+ ports and 4x25G SFP28 ports. 

S5860-48XMG-U/S5860-48XMG has 48x10G copper ports, 4x25G SFP28 ports and 2x40G QSFP+ ports.

Support FS

model N8560-32C

PICOS 4.4.3.

8 only release for FS

model N8560-32C.

N8560-

32C has 32x100G QSFP28 ports.

Support FS Models S5860-20SQ and S5860-24XB-U

PICOS 4.4.3.3 release for FS models S5860-20SQ and S5860-24XB-U.

S5860-20SQ has 20x10G SFP+ ports, 4x25G SFP28 ports and 2x40G QSFP+ ports.

S5860-24BX-

U has

24x10G copper

ports, 4x10G SFP+

ports and

4x25G SFP28 ports.

Support FS

Models S5810-48TS

, S5810-48FS, S5810-28FS and S5810-28TS

PICOS 4.4.3.

2 release for FS

S5810 Series switches.

S5810-48TS

has 48x1G copper ports, 4x10G SFP+ ports.

Support FS models N5850-48S6Q,N8550-48B8C and N8550-32C

From 4.4.2.2 PICOS support FS switches N5850-48S6Q, N8550-48B8C and N8550-32C.
N5850-48S6Q has 48x10G SFP+ ports, 6x40G QSFP ports.
N8550-48B8C has 48x25G SFP28 ports, 8x100G QSFP28 ports and 2x10G SFP+ ports.
N8550-32C has 32x100G QSFP28 ports, 2x10G SFP+ ports.

[Telnet] Pica8 Switch can Telnet Remote Devices

PICOS switch supports to function as telnet client, to telnet remote devices. Please have the details by reference document telnet.

Add MVRP/GVRP Timer Configuration CLI

Support to specify join-timer/leave-timer/leaveall-timer value for MVRP and GVRP in PICOS CLI. Please have the details by reference document Multicast VLAN Registration (MVR) and GVRP.

[New Feature] Support EFM OAM

EFM OAM works in the data link layer, provides the mechanisms that is useful for monitoring link operation such as remote loopback control. PICOS 4.4.3 supports OAM link discovery and remote loopback. However, link monitoring and event notification are not supported yet. Please have the details by reference document Configuring EFM OAM.

[New Feature] Support RESTCONF

RESTCONF is a network configuration management protocol which is developed based on the integration of NETCONF and HTTP protocols. RESTCONF works in Client-Server architecture, where the client can obtain configuration data and status data information from the server. Please have the details by reference document Configuring RESTCONF.

Support ERPS

ERPS (Ethernet Ring Protection Switching) is a L2 protocol used to provide fast and reliable protection against link and switch node failures in an Ethernet network ring topology. It ensures fast failover and minimal traffic disruption in case of a node or link failure. In 4.4.2, sub-ring, FS (Force Switch) and MS (manual switch) are not supported. Please have the details by reference document Configuring ERPS.

Support MVR

MVR (Multicast VLAN Registration) allows the multicast traffic to be forwarded across VLANs based on IGMP multicast group membership. Commonly MVR is enabled on the access switches in order to reduce unnecessary bandwidth consumption in case of forwarding multicast traffic to multiple receiver VLANs. Please have the details by reference document Multicast VLAN Registration (MVR).

Support GVRP

GVRP (GARP VLAN Registration Protocol) is used for automatic VLAN configuration. With GVRP enabled, the connected switches can dynamically exchange VLAN information and automatically configure VLAN on the relevant ports. GVRP reduces the administrative overhead of VLAN management and ensure consistent VLAN configuration throughout the network. Please have the details by reference document GVRP.

Support RMON

Based on SNMP, RMON (Remote Network Monitoring) monitors network status and behavior remotely, and gives historical data for performance and traffic analysis and optimization. In 4.4.2, we support 4 RMON groups, namely, Statistics (group 1), History (group 2), Alarm (group 3) and Event (group 9). Please have the details by reference document Remote Network Monitoring (RMON).

Support RIP and RIPng

As a distance-vector routing protocol, RIP (Routing Information Protocol) facilitates routing information exchange between routers in IP networks. The routing tables are exchanged periodically between routers, and the information about network destinations and associated metrics (such as hop count) is used to determine the best paths. RIPng (RIP Next Generation) is an extension of RIP that supports IPv6. Please have the details by reference document RIP/RIPng Configuration.

Query the Information of NAC Sessions from SNMP

The information of a NAC (Network Access Control) session can be queried from SNMP agent on Pica8 switch. There is no standard SNMP MIB addressing NAC data. Therefore, a new table, dot1xAuthSessionTable, is added to Pica8 private SNMP MIB to support this feature.

Multicast RPF Check

Multicast RPF (Reverse Path Forwarding) check is a mechanism to prevent multicast traffic loop. The multicast traffic not received on the its RPF interface should be discarded. The RPF interface can be identified by looking up the unicast routing table.

Enable EVPN Mutihoming Horizon Split Filtering non-TD3 Platforms

In an EVPN Mutihoming site, the bridged traffic received from an ES (Ethernet Segment) peer and destined to a downstream multihomed device should be discarded by means of the HSF (Horizon Split Filtering) which doesn't work on non-TD3 platforms in previous versions. In 4.4.2, EVPN Mutihoming HSF is enabled on TD2, Tomahawk, and Maverick platforms.

Enhancement on CLI Command "run show dot1x..."

Don't display the duplicate downloadable or dynamic ACL rules of each authorized NAC clients when execute "“run show dot1x interface gigabit-ethernet xxxx". Instead, it can have the detailed downloadable or dynamic ACL rules by executing the separate operational CLI commands “run show dot1x downloadable filter XXXX“ or "run show dot1x dynamic filter XXXX” respectively.

Clean up PIM/IGMP

Add CLI commands under operational mode to clean up multicast routes and statistic counters of PIM and IGMP.

PIM over GRE

PIM can be configured on GRE tunnel interfaces. Multicast traffic can go through GRE tunnels and reach to the receivers. PIM over GRE is used in scenarios where multicast traffic needs to be extended across unicast networks or when multicast traffic needs to be isolated from certain parts of the network. This feature is not supported on N22XX platforms.

Support BGP dot & dot+ AS-notation

When configure the BGP AS number, an AS2B and AS4B value can be presented by using two numbers separated by a period.
XorPlus/New Feature

DHCP Relay over GRE

With DHCP relay enabled, to have the IP address, the DHCP DISCOVERY and REQUEST packets from a host can go through a GRE tunnel to reach the remote DHCP server. And on the other hand, the DHCP OFFER and ACKNOWLEDGE packets from the DHCP server can return back to the host through the GRE tunnel. Both IPv4 and IPv6 are supported in case of DHCP relay over GRE.

Support EVPN MAC Mobility

When a host moves from one Ethernet segment to another segment in the EVPN network, Provider Edge (PE) switches will identify the host MAC address from its local interfaces or from remote PE devices. By means of MAC mobility extended community, the PE switches can determine the correct location of the MAC address location. With EVPN MAC mobility, the MAC address will not be learned on multiple interfaces on a specific PE switch. That could prevent traffic loop in case such as VRRP over EVPN network.

Overlay Host Routes over VPLAG

S5810-48FS has 48x1G SFP ports, 4x10G SFP+ ports.
S5810-28FS has 8x1G copper ports, 28x1G SFP ports, 4x10G SFP+ ports. The 8x1G copper ports and first 8x1G SFP ports are combo ports.
S5810-28TS has 28x1G copper ports, 4x1G SFP ports, 4x10G SFP+ ports. The last 4x1G copper ports and 4x1G SFP ports are combo ports.

Support FS model S5810-48TS-P

PICOS 4.4.3.1 only release for FS model S5810-48TS-P.
S5810-48TS-P has 48x1G copper ports, 4x10G SFP+ ports.

Support FS models N5850-48S6Q,N8550-48B8C and N8550-32C

From 4.4.2.2 PICOS support FS switches N5850-48S6Q, N8550-48B8C and N8550-32C.
N5850-48S6Q has 48x10G SFP+ ports, 6x40G QSFP ports.
N8550-48B8C has 48x25G SFP28 ports, 8x100G QSFP28 ports and 2x10G SFP+ ports.
N8550-32C has 32x100G QSFP28 ports, 2x10G SFP+ ports.

Support AS4625-54P and AS4625-54T

AS4625-54P and AS4625-54T are Gigabit platforms of AS4625-N series. Each of these 2 platforms has 48x1000BASE-T ports, and 6x10G SFP+ ports and 2x1G me ports path to CPU. AS4625-54P is a PoE capable platform of which the ports from ge-1/1/41 to ge-1/1/48 support IEEE802.3bt standard with up to 90W power delivery, and the rest 1000BASE-T ports from ge-1/1/1 to ge-1/1/40 supports IEEE802.3at and IEEE802.3af with up to 30W delivery.

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.

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.

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.

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.

Ingress Buffer

Supports ingress buffer management, including guaranteed/shared/headroom management. Please have the details by reference document Configuring PFC Buffer.

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.

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.

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.

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 /wiki/spaces/PicOS44sp/pages/178585601.

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.

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.

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.

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.

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).

PIM over GRE

PIM can be configured on GRE tunnel interfaces. Multicast traffic can go through GRE tunnels and reach to the receivers. PIM over GRE is used in scenarios where multicast traffic needs to be extended across unicast networks or when multicast traffic needs to be isolated from certain parts of the network. This feature is not supported on N22XX platforms.

Support BGP dot & dot+ AS-notation

When configure the BGP AS number, an AS2B and AS4B value can be presented by using two numbers separated by a period.
XorPlus/New Feature

DHCP Relay over GRE

With DHCP relay enabled, to have the IP address, the DHCP DISCOVERY and REQUEST packets from a host can go through a GRE tunnel to reach the remote DHCP server. And on the other hand, the DHCP OFFER and ACKNOWLEDGE packets from the DHCP server can return back to the host through the GRE tunnel. Both IPv4 and IPv6 are supported in case of DHCP relay over GRE.

Support EVPN MAC Mobility

When a host moves from one Ethernet segment to another segment in the EVPN network, Provider Edge (PE) switches will identify the host MAC address from its local interfaces or from remote PE devices. By means of MAC mobility extended community, the PE switches can determine the correct location of the MAC address location. With EVPN MAC mobility, the MAC address will not be learned on multiple interfaces on a specific PE switch. That could prevent traffic loop in case such as VRRP over EVPN network.

Overlay Host Routes over VPLAG

The outgoing ports of EVPN overlay host routes can be VPLAG ports when execute "run show route forward-host ipv4 all". Therefore, in case of EVPN multi-homing deployment, the L3 traffic from a host can be routed out VPLAG port and reach to the remote host via VXLAN tunnel.

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.

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).

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.