PicOS® Configuration Guide V4.5

Aug 22, 2025 - 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

Aug 22, 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

PicOS® Quick Configuration Guide

Aug 22, 2025 - PicOS® Quick Configuration Guide Chapter 1 Initial Setup Before performing the following operations, you should make sure that the device has been installed successfully. For detailed information of installing Picos, see Installing or Upgrading PICOS 1.1 Powering on the Switch Connect the switch to a power supply through the power cord, annd then press the power button to power on the switch 1.2 Logging in Switch through the Console Port For initial system configuration, you should connect the switch to a termihal through the Console port Procedure Step1: Connect the console port of the switch to the serial port ofa PC through a console cable, as shown in the figure below. image.png Figure 1-1 Connetion of Console cable Step2: Open a terminal emulator (e.g., PuTTY) and configure it with the appropriate COM port settings, which should be the same with the switch related parameters. As shown in the figure below. image.png Figure 1-2 Serial Settings of Terminal Emulator Step3: Enter the default administrator name admin and password pica8 at the PICOS login and password prompts, and press Enter. Change the default password according to prompts, press Enter, and you can successfully log in CLI. As shown in the figure below. image.png Figure 1-3 Password Modification for First login Chapter 2 Basic Configuration 2.1 Entering CLI Configuration Mode PicOS supports different CLI modes, which are indicated by different prompts. Some commands can only be run in certain modes. Operation mode When log in PicOS CLI, you are in the operation mode by default. YYou can execute some basic configurations in this mode such as clear and show, etc. > indicates the operation mode,as shown in the figure below. image.png Figure 2-1 Prompt of Operation Mode Configuration mode You can configure the switch function in this mode, such as interface, routing, etc. Run configure in the operation mode to enter the configuration mode, and run exit to return to the operation mode. # indicates the configuration mode, as shown in the figure below. image.png Figure 2-2 Prompt of Configuration Mode Linux shell mode Run start shell sh in the operation mode to enter the Linux shell mode, and run exit to return to the operation mode. ~$ indicates the Linux shell mode, as shown in the figure below. image.png Figure 2-3 Prompt of Linux Shell Mode 2.2 Configuring a Host Name 2.2.1 Overview A host name distinguishes one device from another. The default host name is system name PICOS. You can modify the host name as required. 2.2.2 Procedure Step1:In the configuration mode, specify or modify a host name for the switch. set system hostname Step2: Commit the configuration. commit 2.2.3 Verifying the Configuration After the configuration is completed, in the configuration modeuse run show system name command to view the new host name. 2.2.4 Other Configurations To reset the host name to default, use delete system host name ccommand 2.3 Configuring the Management IP Address 2.3.1 Overview To facilitate the device management and meet the requirement of sepaarating the management traffic from the data traffic the switch supports the management interface. By default, the management interface is etho and the IP address is null 2.3.2 Procedure Step1: In the configuration mode, specify the IP address for management interface etho. set system management-ethernet eth0 ip-address{IPv4 | IPv6} Step2: Commit the configuration. commit 2.3.3 Verifying the Configuration After the configuration is completed, in the configuration mode,use run show system management-ethernet command to view the MAC address, IP address, state and traffic statistics. 2.3.4 Other Configurations. To clear the configuration of management interface, use delete system management-ethernet eth0 ip-address command. Chapter 3 Network Configuration 3.1 Configuring an Interface Physical interface: exists on interface cards, which can be used for imanagement and service. Management interface: the switch supports a management interface eth0 by default, which is used to log in devices for configuration and management. For detailed information for the management interface, see Configuring the Management IP Address. Service interface: can be used for service transmission, which includes Layer 2 Ethernet interfaces and Layer 3 Ethernet interfaces. By default, service interfaces of switch are all Layer 2 interfaces. To configure a Layer 2 interface as a Layer 3 interface, see the followinig chapter. Logical interface: not exists physically and is configured manually,which is used for service transmission. It includes Layer 3 interfaces, routed interfaces, loopback interfaces,etc. It includes the following chapters: 3.1.1 Configuring a loopback interface 1. Overview The loopback interface is always up to ensure network reliabiliity, which has the following features: It is always up and has the loopback feature. It can be configured with the mask of all 1s. Based on the features, the loopback interface has the following applications: The IP address of a loopback interface is specified as the source address of packets to improve network reliability. When no Router ID is configured for dynamic routing protocols, the maximum IP address of the loopback interface is configured as the router ID automatically. 2. Procedure Step1: In the configuration mode, specify the name and IP address for the loopback interface. set l3-interface loopback address prefix-length 32 set l3-interface loopback address prefix-length 128 Step2: Commit the configuration. commit 3. Verifying the Configuration After the configuration is completed, in the configuration mode, use run show l3-interface loopback command to view the state, IP address, description and traffic statistics. 4. Other Configurations By default, the loopback interface is enabled when created. To disable the loopback interface, use set l3-interface loopback disable command. To clear the configuration of loopback interface, use delete l3-interface loopback interface command. 3.1.2 Configuring a Routed interface 1. Overview All Ethernet ports of switch are Layer 2 interfaces by default. When you need to use an Ethernet port for Layer 3 communication, you can enable the Ethernet port as a routed interface. The routed interface is a Layer 3 interface which can be assigned an IP address and can be configured with a routing protocol to connect to other Layer 3 routing devices. 2. Procedure Step1: In the configuration mode, set reserved VLANs for the use of routed interface. set vlansreserved-vlan reserved-vlan : specifies the reserved VLANs. The valid VLAN numbers range is 2-4094. User can specify a range of VLAN numbers, e.g. 2,3,50-100. System supports up to 128 reserved VLANs Step2: Select a physical interface as the routed interface and specify a name. set interface gigabit-ethernet routed-interface name routed-interface name : specifies a routed interface name Note: The name must start with "rif-", for example, rif-ge1. Step3: Enable the routed interface. set interface gigabit-ethernet routed-interface enable true Step4: Configure an IP address for the routed interface. set l3-interface routed-interface address prefix-length prefix-length : specifies the network prefix length. The range is 4-32 for IPv4 address, and 1-128 for IPv6 address Step5: Commit the configuration. commit 3.Verifying the Configuration After the configuration is completed, in the configuration mode, use run show 13- interface routed-interface command to view the state, IP address, MAC address, VLAN, MTU, description and traffic statistics. 4. Other Configurations To disable the routed interface, use set interface gigabit-ethernet command. 3.1.3 Configuring a VLAN Interface 1. Overview By default, the native VLAN of all physical interfaces is VLAN 1, which can implement Layer 2 communication. To implement Layer 3 communication between users in different VLANs and network segments, you can configure the VLAN interface, which is a Layer 3 logical interface. 2. Procedure Step1: In the configuration mode, create a VLAN. Note: The VLAN ID has been pre-configured in system from version 4.3.2 and you don’t need to configure it. set vlans vlan-id vlan-id : specifies the VLAN tag identifier. The valid VLAN numbers range 1-4094. User can specify a range of VLAN numbers, e.g. 2,3,5-100. Step2: Specify the created VLAN as the native VLAN for a physical interface. set interface gigabit-ethernet family ethernet-switching native-vlan-id Step3: Associate a Layer 3 interface with the VLAN. set vlans vlan-id l3-interface l3-interface : specifies a name for the Layer 3 interface. Step4: Configure an IP address for the VLAN interface. set l3-interface vlan-interface address prefix-length Step5: Commit the configuration. commit 3. Verifying the Configuration After the configuration is completed, in the configuration mode, use run show 13-interface vlan-interface command to view the state, IP address, MAC address, VLAN, MTU, description and traffic statistics. 4. Other Configurations To clear the configuration of VLAN interface, use delete l3-interface vlan-interface command. 3.2 Configuring the Routing Routing is a process of forwarding packets from one network to a destination address in another network. The implement of route selection and packet forwarding is based on various routes stored in the routing table. To maintain the routing table, you can manually add or configure different routing protocols. The switch supports direct routing, static routing and dynamic routing. Direct routing: discovered by a data link layer protocol. Static routing: manually configured. Dynamic routing: discovered by a dynamic routing protocol. It includes the following chapters: 3.2.1 Configuring the Static Routing 1. Overview The static routing is manually configured, which requires low system performance and is applicable to small-size network with simple and stable topologies. 2. Procedure Before configuring the routing, make sure that the Layer 3 interface has been configured. Step1: By default, the IP routing function is disabled. In the configuration mode, enable the IP routing function. set ip routing enable true Step2: Specify the destination address, and configure one of next-hop IP address and outgoing interface as needed. set protocolsstatic route next-hop route : specifies a destination IPv4 or IPv6 address and the prefix length of 1 to 32 for IPv4 and 1 to 128 for IPv6. next-hop : specifies the next-hop IP address. set protocolsstatic interface-route interface interface : specifies the Layer 3 interface as an outgoing interface. The value could be a VLAN interface, loopback interface, routed interface or sub-interface. Step3: Commit the configuration. commit 3. Verifying the Configuration After the configuration is completed, in the configuration mode, use run show route static command to view all static routing entries. 4. Other Configurations To clear the configuration of static interface, use delete protocolsstatic route command. 3.2.2 Configuring the Dynamic Routing The dynamic routing is based on algorithm, which requires higher system performance. It is applicable to network with a large number of Layer 3 devices, and can automatically adapt to the changeable network topology. The switch supports multiple dynamic routing, such as OSPF, BGP, IS-IS, etc. OSPF is the IGP (Interior Gateway Protocol) recommended by PicOS. Take the OSPF routing as an example to introduce how to configure a dynamic routing. 1. Overview OSPF (Open Shortest Path First) is developed by IETF (Internet Engineering Task Force), which uses the shortest path first (SPF) algorithm to calculate a shortest path tree (SPT) to all destination addresses based on the network topology, and is advertised through link state advertisements (LSAs). It is applicable to the network with several hundred devices, such as small and medium-sized enterprises networks. PicOS supports OSPFv2 and OSPFv3, which is respectively intended for IPv4 and IPv6. 2. Procedure Before configuring the routing, make sure that the Layer 3 interface has been configured. Step1: By default, the IP routing function is disabled. In the configuration mode, enable the IP routing function. set ip routing enable true Step2: Set the OSPF router ID. set protocols ospf router-id router-id : specifies the OSPF router ID, which can uniquely identify the switch within the domain. The value is in IPv4 dotted decimal format Step3: Add the specified network segment to an area. Area 0 is required. set protocols ospf network area {} network : specifies the network prefix and prefix length in IPv4 format. area {}: specifies the OSPF area, the value could be in IPv4 dotted decimal format or a integer ranging from 0 to 4294967295. Step4: Commit the configuration. commit 3. Verifying the Configuration After the configuration is completed, in the configuration mode, use run show route ospf command to view all OSPF routing entries. 4. Other Configurations To delete the OSPF routing configuration, use delete protocols ospf command. Chapter 4 Security Configuration 4.1 Configuring an ACL 1. Overview ACL (Access Control List) is packet filtering rules through defining conditions of source addresses, destination addresses, interfaces, etc. The switch permits or denies packets according to the configured action of ACL rules. ACL can manage network access behaviors, prevent network attacks, and improve bandwidth utilization through accurately identifying and controlling packets, which ensures network security and service quality. 2. Procedure Step1: Set the sequence number of priority. set firewall filter sequence sequence : specifies the sequence number. Smaller values represent higher priorities. The range is 0-9999 Step2: Specify the source address and source port to filter matched packets. set firewall filter sequence from {source-address-ipv4 | source-address-ipv6 < address/prefix-length > | source-mac-address | source-port } source-port : specifies the source port number or port number range, for example, 5000 or 7000..7050. Step3: Specify the execution action for packets matching the filter. set firewall filter sequence then action {discard | forward} action {discard | forward}: discards or forwards matched packets Step4: Specify the physical interface, VLAN interface or routed interface to filter matched incoming and egress packets. set firewall filter input {interface | vlan-interface | routed-interface } set firewall filter output {interface | vlan-interface | routed-interface } Step5: Commit the configuration. commit 3. Verifying the Configuration After the configuration is completed, in the configuration mode, use run show filter ] command to view the matching condition of specified filter. 4. Other Configurations To delete the configured filter, use delete firewall filter command. 4.2 Configuring the SSH Access 1. Overview SSH (Secure Shell) is an encryption network protocol, which can perform secure access and file transmission in the unsecured network. It performs data exchange through a secure channel, which is established based on TCP. The default port is 22, which can be changed as required for security purposes. 2. Procedure By default, the SSH service is enabled. You can log in switch through SSH protocol by directly access eth0. Besides, if you want to remotely log in and manage the switch through the Layer 3 interface, you should configure as follows: Step1: In the configuration mode, specify the loopback interface, VLAN interface or routed interface as the inband management port, both management traffic and data plane traffic can be transmitted through the specified interface. The specified interface should be in the default VRF. setsystem inband {loopback | vlan-interface | routed-interface } Step2: (Optional) Set the limit number of SSH connections. setsystem servicesssh connection-limit connection-limit : specifies the maximum number of allowed connections, the valid number ranges 0-250. Default value is 0, which removesthe connection limit Step3: (Optional) Specify the listening port number of SSH server. setsystem servicesssh port port : specifies the listening port number of the SSH server. The value is an integer ranging from 1 to 65535. Th default value is 22 Step4: Commit the configuration. commit 3. Verifying the Configuration After the configuration is completed, use ssh admin@ -p to check whether the switch can be accessed through SSH. 4. Other Configurations To disable the SSH service, use set system servicesssh disable true command. To delete the SSH configuration, use delete system servicesssh command. Chapter 5 Typical Configuration Example 5.1 Overview Take the following topology as an example to introduce how to implement communication between PC1 and PC2. image.png Figure 5-1 Topology of Access Network The data plan is shown as below. Device Interface VLAN and IP Address Switch A te-1-1-1 VLAN: 10 IP address: 10.10.10.1/24 te-1-1-2 VLAN: 4 IP address: 10.10.4.1/24 te-1-1-3 VLAN: 5 IP address: 10.10.5.2/24 Switch B te-1-1-1 VLAN: 3 IP address: 10.10.3.1/24 te-1-1-2 VLAN: 4 IP address: 10.10.4.2/24 Switch C te-1-1-1 VLAN: 2 IP address: 10.10.2.1/24 te-1-1-3 VLAN: 5 IP address: 10.10.5.1/24 PC1 10.10.3.8/24 PC2 10.10.2.8/24 5.2 Procedure Before configuring the following steps, make sure you have logged in the specified switch through Console port or SSH. For detailed information, see Initial Setup and Configuring the SSH Access. Step1: In the configuration mode, configure the host name of switch respectively as SwitchA, SwitchB and SwitchC. Run the same command on other switches to change the hostname as SwitchB and SwitchC. 1.admin@PICOS> configure 2.admin@PICOS# set system hostname SwitchA 3.admin@PICOS# commit 4.admin@SwitchA# Step2: Configure the interface and VLAN. Switch A Interface te-1-1-1: 1.admin@SwitchA# set vlans vlan-id 10 2.admin@SwitchA# set interface gigabit-ethernet te-1/1/1 family ethernet-switching native-vlan-id 10 3.admin@SwitchA# set vlans vlan-id 10 l3-interface vlan10 4.admin@SwitchA# set l3-interface vlan-interface vlan10 address 10.10.10.1 prefix-length 24 5.admin@SwitchA# commit Interface te-1-1-2: 1.admin@SwitchA# set vlans vlan-id 4 2.admin@SwitchA# set interface gigabit-ethernet te-1/1/2 family ethernet- admin@SwitchA# switching native-vlan-id 4 3.admin@SwitchA# set vlans vlan-id 4 l3-interface vlan4 4.admin@SwitchA# set l3-interface vlan-interface vlan4 address 10.10.4.1 prefix-length 24 5.admin@SwitchA# commit Interface te-1-1-3: 1.admin@SwitchA# set vlans vlan-id 5 2.admin@SwitchA# set interface gigabit-ethernet te-1/1/3 family ethernet-switching native-vlan-id 5 3.admin@SwitchA# set vlans vlan-id 5 l3-interface vlan5 4.admin@SwitchA# set l3-interface vlan-interface vlan5 address 10.10.5.2 prefix-length 24 5.admin@SwitchA# commit Switch B Interface te-1-1-1: 1.admin@SwitchB# set vlans vlan-id 3 2.admin@SwitchB# set interface gigabit-ethernet te-1/1/1 family ethernet-switching native-vlan-id 3 3.admin@SwitchB# set vlans vlan-id 3 l3-interface vlan3 4.admin@SwitchB# set l3-interface vlan-interface vlan3 address 10.10.3.1 prefix-length 24 5.admin@SwitchB# commit Interface te-1-1-2: 1.admin@SwitchB# set vlans vlan-id 4 2.admin@SwitchB# set interface gigabit-ethernet te-1/1/2 family ethernet-switching native-vlan-id 4 3.admin@SwitchB# set vlans vlan-id 4 l3-interface vlan4 4.admin@SwitchB# set l3-interface vlan-interface vlan4 address 10.10.4.2 prefix-length 24 5.admin@SwitchB# commit Switch C Interface te-1-1-1: 1.admin@SwitchC# set vlans vlan-id 2 2.admin@SwitchC# set interface gigabit-ethernet te-1/1/1 family ethernet-switching native-vlan-id 2 3.admin@SwitchC# set vlans vlan-id 2 l3-interface vlan2 4.admin@SwitchC# set l3-interface vlan-interface vlan2 address 10.10.2.1 prefix-length 24 5.admin@SwitchC# commit Interface te-1-1-3: 1.admin@SwitchC# set vlans vlan-id 5 2.admin@SwitchC# set interface gigabit-ethernet te-1/1/3 family ethernet-switching native-vlan-id 5 3.admin@SwitchC# set vlans vlan-id 5 l3-interface vlan5 4.admin@SwitchC# set l3-interface vlan-interface vlan5 address 10.10.5.1 prefix-length 24 5.admin@SwitchC# commit Step3: Configure the IP address and default gateway of PC1 and PC2. PC1: 1.root@UbuntuDockerGuest-1:~# ifconfig eth0 10.10.3.8/24 2.root@UbuntuDockerGuest-1:~# route add default gw 10.10.3.1 PC2: 1.root@UbuntuDockerGuest-2:~# ifconfig eth0 10.10.2.8/24 2.root@UbuntuDockerGuest-2:~# route add default gw 10.10.2.1 Step4: Configure the routing. You can configure the static routing or OSPF routing to connect network. Connecting network through the static routing Switch A: 1.admin@SwitchA# set ip routing enable true 2.admin@SwitchA# set protocols static route 10.10.2.0/24 next-hop 10.10.5.1 3.admin@SwitchA# set protocols static route 10.10.3.0/24 next-hop 10.10.4.2 4.admin@SwitchA# commit Switch B: 1.admin@SwitchB# set ip routing enable true 2.admin@SwitchB# set protocols static route 0.0.0.0/0 next-hop 10.10.4.1 3.admin@SwitchB# commit Switch C: 1.admin@SwitchC# set ip routing enable true 2.admin@SwitchC# set protocolsstatic route 0.0.0.0/0 next-hop 10.10.5.2 3.admin@SwitchC# commit Connecting network through the OSPF routing Switch A: 1.admin@SwitchA# set l3-interface loopback lo address 1.1.1.1 prefix-length 32 2.admin@SwitchA# set protocols ospf router-id 1.1.1.1 3.admin@SwitchA# set protocols ospf network 10.10.4.0/24 area 0 4.admin@SwitchA# set protocols ospf network 10.10.10.0/24 area 0 5.admin@SwitchA# set protocols ospf network 10.10.5.0/24 area 1 6.admin@SwitchA# commit Switch B: 1.admin@SwitchB# set l3-interface loopback lo address 2.2.2.2 prefix-length 32 2.admin@SwitchB# set protocols ospf router-id 2.2.2.2 3.admin@SwitchB# set protocols ospf network 10.10.4.0/24 area 0 4.admin@SwitchB# set protocols ospf network 10.10.3.0/24 area 0 5.admin@SwitchB# commit Switch C: 1.admin@SwitchC# set l3-interface loopback lo address 3.3.3.3 prefix-length 32 2.admin@SwitchC# set protocols ospf router-id 3.3.3.3 3.admin@SwitchC# set protocols ospf network 10.10.2.0/24 area 1 4.admin@SwitchC# set protocols ospf network 10.10.5.0/24 area 1 5.admin@SwitchC# commit 5.3 Verifying the Configuration View the routing table of each switch. 1. Static Routing: image.png Figure 5-2 Static Routing Entries of SwitchA image.png Figure 5-3 Static Routing Entries of SwitchB image.png Figure 5-4 Static Routing Entries of SwitchC 2. OSPF Routing: image.png Figure 5-5 OSPF Routing Entries of SwitchA image.png Figure 5-6 OSPF Routing Entries of SwitchB image.png Figure 5-7 OSPF Routing Entries of SwitchC Run Ping command to check the connectivity between PC1 and PC2. 1. PC1 ping PC2: image.png Figure 5-8 Result of PC1 Ping PC2 2. PC2 ping PC1: image.png Figure 5-9 Result of PC2 Ping PC1

PicOS® Software Release Notes V4.5.0

Jul 15, 2025 - 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. Hardware Ticket ID Release Description - 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.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.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 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 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.

PicOS® CLI Reference Guide V4.4.5

Jul 15, 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

PicOS® Configuration Guide V4.4.5

Jul 15, 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

PicOS® Software Release Notes V4.4.5

Jul 15, 2025 - PicOS® Software Release Notes V4.4.5 Introduction These notes summarizes PicOS 4.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. Notice: PicOS 4.4.5 and 4.4.5.1 are beta releases. Users should be aware that there may be some instability or known limitations in these versions. We highly value any feedback or issues reported during this phase, as it will help us refine and enhance the product. PicOS 4.4.5.7 is the General Availability (GA) release, marking a stable, production-ready version. This release incorporates fixes for issues found during the beta phase and includes performance enhancements, stability improvements, and full platform support, with the exception of the S3410 series switch. PICOS 4.4.5.24 is officially released as the General Availability (GA) version for the S3410 and S3270 series. This release delivers production-grade stability and is recommended for deployment in production environments. Hardware Release Description 4.4.5.24 Support FS S3270 and S3410 Series Switches S3270 Series: S3270-10TM, S3270-24TM, S3270-48TM, S3270-10TM-P and S3270-24TM-P S3410 Series: S3410L-24TF, S3410L-24TF-P, S3410L-48TF, S3410-24TS, S3410-24TS-P, S3410-48TS, S3410-48TS-P, S3410C-16TF, S3410C-16TF-P, S3410C-8TMS-P and S3410C-16TMS-P 4.4.5.1 Support FS S3410 Series Switches PicOS 4.4.5.1 release for FS models S3410L-24TF, S3410L-24TF-P, S3410-24TS, S3410-24TS-P, S3410C16TF, S3410C-16TF-P, S3410C-16TMS-P and S3410C-8TMS-P. 4.4.5 Support FS Models S3410 Series: S3410L-24TF, S3410L-24TF-P, S3410-24TS, S3410-24TS-P, S3410C-16TF, S3410C-16TF-P, S3410C-16TMS-P, S3410C-8TMS-P S5810 Series: S5810-48TS-P, S5810-28TS, S5810-28FS, S5810-48TS, S5810-48FS S5860 Series: S5860-20SQ, S5860-24XB-U, S5860-24MG-U, S5860-24XMG, S5860-48XMG-U, S5860- 48XMG, S5860-48MG-U S5870 Series: S5870-48T6BC-U, S5870-48T6BC, S5870-48MX6BC-U N5850 Series: N5850-48S6Q, N5850-48X6C N8550 Series: N8550-48B8C, N8550-32C, N8550-64C N8560 Series: N8560-32C N9550 Series: N9550-32D New Features Changes Specification PicOS-4.4.5 Layer 2 and Layer 3 Release Description 4.4.5 Support IS-IS IS-IS (Intermediate System to Intermediate System) is an Interior Gateway Protocol (IGP) used within an autonomous system. It is a link-state protocol that employsthe Shortest Path First (SPF) algorithm for routing calculations. For more information, see the documentation IS-IS Configuration. 4.4.5 Support OSPFv2/OSPFv3 GR OSPF Graceful Restart (GR) ensures that routers running the OSPF protocol can maintain normal service forwarding during a primary-backup switchover or an OSPF protocol restart. For more information, see the documentation OSPF GR. 4.4.5 Support IPv6 Source Guard IPv6 Source Guard is a security feature designed to filter IPv6 traffic on untrusted Layer 2 ports. It helps switches or routers reject traffic originating from addresses not stored in the IPv6 binding table. IPv6 Source Guard discards packets with IPv6 source addresses absent from the binding table, which contains entriesfor the link-local addresses of hosts. For more information, see the documentation IPv6 Source Guard (IPSG for IPv6). 4.4.5 Support IPv6 DHCP Guard IPv6 DHCP Guard prevents replies and advertisements from unauthorized DHCP servers and relay agents. It filters DHCPv6 response messages based on criteria such as the source address of the DHCPv6 message, the IPv6 address assigned to the user, or the priority of the DHCPv6 server. This ensures that DHCPv6 clients obtain prefixes, addresses, or other parameters from authorized DHCPv6 servers. For more information, see the documentation DHCPv6 Guard Configuration. 4.4.5 Support IPv6 DHCP Snooping DHCPv6 Snooping is a security feature that intercepts DHCPv6 messages between DHCPv6 Servers and DHCPv6 Clients. It establishes and maintains a DHCPv6 Snooping binding table that records information about DHCPv6 Clients, including user MAC addresses, IPv6 addresses, lease durations, VLAN IDs, and interfaces. The device uses thistable to analyze and process messages, filter out attack packets, and provide security services for DHCPv6. For more information, see the documentation Configuring DHCPv6 Snooping (IPv6). 4.4.5 Support PFC Watchdog The PFC (Priority-based Flow Control) mechanism allows downstream devices to send PFC pause framesrequesting upstream devices to pause traffic transmission. During network anomalies, this mechanism may propagate PFC pause framesthroughout the entire network, potentially leading to a PFC deadlock where traffic forwarding halts. The PFC Watchdog is designed to detect and automatically recover from PFC deadlocks, ensuring network stability and traffic flow. For more information, see the documentation Lossless Network Configuration. 4.4.5 ECMP Hash Enhancement The ECMP (Equal-Cost Multi-Path) hash enhancement supports the following load balancing modes: Randomized Load Balance, Round-Robin Load Balance and Dynamic Load Balance Normal Mode. For more information, see the documentation Lossless Network Configuration. Fixed Issues PicOS-4.4.5.24 Layer 2 and Layer 3 Release Description 4.4.5.24 [S3000][Upgrade2] nos-rollback the older version:older version information needs to be displayed. Fixed in 4.4.5.16 4.4.5.24 [S3000][NTP] "run show system NTP-status" needs to show "NTP Server Sync information". Fixed in 4.4.5.16 4.4.5.24 [S3410][Upgrade2] talent connection switch:Upgrade2 to a new version should not require manually stopping picos. Fixed in 4.4.5.16 4.4.5.24 [S3410C-8TMS-P] reboot appear error log. Fixed in 4.4.5.16 4.4.5.24 [CLI] Commit does not save running config to the flash and need using copy running-config startup-config. Fixed in 4.4.5.16 4.4.5.24 [SSH limitation] The ssh connection should support user-defined limits on the number of connections and connection duration. Fixed in 4.4.5.16 4.4.5.24 [S5810-48FS][AAA][Radius] wrong prompt message when superuser configuration commands. The issue was introduced while fixing Bug17995, when superuser commit configurations will be failed. This issue resolved in 4.4.5.24. 4.4.5.24 [S3410C-16TMS-P] The switch cannot print logs. Fixed in 4.4.5.24 4.4.5.24 [S3410/S3270] rboot install failed on some platforms. Fixed in 4.4.5.24 4.4.5.24 [S3410/S3270] support SSH Weak MAC Algorithms when do ssh connection. Fixed in 4.4.5.24 4.4.5.24 [S3410/S3270] SSH: modify max supported ssh number and max ssh connected number. Fixed in 4.4.5.24 4.4.5.24 [S3410] diagnostic support POE module check information. Fixed in 4.4.5.24 PicOS-4.4.5.7 Layer 2 and Layer 3 Release Description 4.4.5.7 [Blackbox Upgrade] Enhancement for Blackbox Upgrade Behavior modification for upgrades on S5810 and S5860 Series Switches: When upgrading via console port, users must manually stop PicOS before proceeding. When upgrading via eth0 or inband, manually stopping PicOS is no longer required. 4.4.5.7 Incorrect Product Name Display in 'show system hwinfo' Command Removed the 'run show system hwinfo' command from S5810 and S5860 Series Switchesto address this issue. 4.4.5.7 [LBD] S5860-48XMG-U does notsupport LBD LBD (Loopback Detection) is now supported on S5860-48XMG-U, S5860-48XMG, and S5860-48MG-U. 4.4.5.7 [Socket] Resolved the issue where the error log 'local0.err : [SIF]Wrong FPM packet' appeared on the S5850- 48S6Q, causing 100% CPU usage. The bug is fixed in 4.4.5. PicOS-4.4.5 Layer 2 and Layer 3 Release Description 4.4.5 [S5810-28TS] DDM Information is Incorrect. 4.4.5 [10G/25G/100G/400G Module] The switch cannot recognize FS 10G/25G/100G/400G modules. The bug isfixed in 4.4.5. 4.4.5 [S5860-48XMG/S5860-24XMG] Fan speed reads 0 due to CPLD hardware upgrade on S5860-48XMG and S5860-24XMG models. The bug is fixed in 4.4.5. 4.4.5 [N8560-32C] Breakout port experiences packet loss. The bug is fixed in 4.4.5. Known Limitations Release Description 4.4.5.24 SSH limit The default value of system services ssh connection-limit is 3 and the max value is 5, the idle-timeout is 3600s. 4.4.5.24 CLI limit Once switch enter linux shell mode, user should use 'exit' enter CLI mode. [S3410] once switch enter linux shell mode, user should use 'exit' back to CLI but cannot execute 'cli' 4.4.5.24 Download Image file If you want to upgrade the PicOS version, please place the installation package in the/mnt/open directory. 4.4.5.24 Upgrade limitation S3410 series switches only allow the use of 'upgrade2' to upgrade PicOS version. S3410 only supports downloading the image file in '/mnt/open' before upgrade2. S3270 series switches only allow the use of 'upgrade' to upgrade PicOS version. S3270 does not support downloading the image file in '/mnt/open' before upgrade. 4.4.5 Not Support OSPF Multi-Instance PicOS 4.4.5 does not support OSPF Multi-Instance. 4.4.5 Not Support Configuring through the WEB Interface PicOS 4.4.5 does not support configuring through the WEB interface. 4.4.5 Not Support Telnet Server PicOS 4.4.5 does not support telnet server.

PicOS® Hardware Compatibility Matrix

Jul 12, 2025 - PicOS® Hardware Compatibility Matrix FS Hardware Compatibility Product Model Configuration Switch ASIC CPU 1G Switch Portfolio S5870-48T6S 48 x 1G 6 x 10G Broadcom Trident III Intel Atom C3508 1G Switch Portfolio S5870-48T6BC 48 x 1G 4 x 25G Broadcom Trident III Intel Atom C3558 1G Switch Portfolio S5870-48T6BC-U 48 x 1G PoE++ 4 x 25G 2 x 100G Broadcom Trident III Intel Atom C3558 1G Switch Portfolio S5870-48MX6BC-U 36 x 2.5G PoE++ 12 x 10G PoE++ 4 x 25G 2 x 100G Broadcom Trident III Intel Atom C3558 1G Switch Portfolio S5810-28TS 24 x 1000BASE-T 4 x 1G 4 x 10G BCM56342 ARMA9 1G Switch Portfolio S5810-48TS 48 x 1G 4 x 10G BCM56340 ARMA9 1G Switch Portfolio S5810-28FS 8x 1000BASE-T 28 x 1G 4 x 10G BCM56342 ARMA9 1G Switch Portfolio S5810-48FS 48 x 1G 4 x 10G BCM56340 ARMA9 1G Switch Portfolio S5810-48TS-P 48 x 1G PoE+ 4 x 10G BCM56340 ARMA9 1G Switch Portfolio S5860-24MG-U 24 x 5GBASE-T/Multi-Gigabit PoE++ 4 x 25G BCM56170 ARMA9 1G Switch Portfolio S3410C-8TMS-P 8 x 1000BASE-T PoE+ 2 x 1000M/2.5G/5GBASE-T 2 x 10G BCM56150 ARMA9 1G Switch Portfolio S3410C-16TMS-P 16 x 1000BASE-T PoE+ 2 x 1000M/2.5G/5GBASE-T 2 x 10G BCM56150 ARMA9 1G Switch Portfolio S3410C-16TF 16 x 1000BASE-T 2 x 1G BCM56150 ARMA9 1G Switch Portfolio S3410C-16TF-P 16 x 1000BASE-T 2 x 1G BCM56150 ARMA9 1G Switch Portfolio S3410-24TS-P 24 x 1000BASE-T PoE+ 2 x Combo 2 x 10G BCM56150 ARMA9 Product Model Configuration Switch ASIC CPU 1G Switch Portfolio S3410-48TS-P 48 x 1000BASE-T PoE+ 2 x Combo 2 x 10G BCM56150 ARMA9 1G Switch Portfolio S3410L-24TF-P 24 x 1000BASE-T PoE+ 4 x 1G BCM56152 ARMA9 1G Switch Portfolio S3410L-24TF 24 x 1000BASE-T 4 x 1G BCM56152 ARMA9 1G Switch Portfolio S3410L-48TF 48 x 1000BASE-T 4 x 1G BCM56152 ARMA9 1G Switch Portfolio S3410-24TS 24 x 1000BASE-T 4 x 10G BCM56150 ARMA9 1G Switch Portfolio S3410-48TS 48 x 1000BASE-T 4 x 10G BCM56150 ARMA9 10G Switch Portfolio N5850-48S6Q 48 x10G 6 x 40G Broadcom Trident II+ Intel Atom C2538 10G Switch Portfolio N5850-48X6C 48 x 10G 6 x 100G Broadcom Trident III Intel Atom C3558 10G Switch Portfolio S5860-20SQ 20 x 10G 4 x 25G 2 x 40G BCM56170 ARMA9 10G Switch Portfolio S5860-24XB-U 24 x 10GBASE-T/Multi-Gigabit PoE++ 4 x 10G 4 x 25G BCM56170 ARMA9 10G Switch Portfolio S5860-24XMG 24 x 10GBASE-T/Multi-Gigabit 4 x 10G 4 x 25G BCM56170 ARMA9 10G Switch Portfolio S5860-48XMG 48 x 10GBASE-T/Multi-Gigabit 4 x 25G 2 x 40G BCM56170 ARMA9 10G Switch Portfolio S5860-48XMG-U 48 x 10GBASE-T/Multi-Gigabit PoE++ 4 x 25G 2 x 40G BCM56170 ARMA9 25G Switch Portfolio N8550-48B8C 48 x 25G 2 x 10G 8 x 100G Broadcom Trident III Intel Xeon D- 1518 100G Switch Portfolio N8550-32C 32 x 100G 2 x 10G Broadcom Trident III Intel Xeon D- 1518 100G Switch Portfolio N8550-64C 64 x 100G Broadcom Tomahawk II Intel Xeon D- 1518 Product Model Configuration Switch ASIC CPU 100G Switch Portfolio N8560-32C(Back-to-Front) 32 x 100G BCM56870 Intel Xeon D- 1527 100G Switch Portfolio N8560-32C(Front-to-Back) 32 x 100G BCM56870 Intel Xeon D- 1527 200G Switch Portfolio N8550-24CD8D 24 x 200G 8 x 400G Broadcom Trident IV Intel Xeon D-1627 400G Switch Portfolio N9550-32D 32 x 400G Broadcom Tomahawk III Intel Xeon D- 1518 400G Switch Portfolio N9550-64D 64 x 400G Broadcom Tomahawk IIII Intel Xeon D- 1627 EDGECORE Networks Hardware Compatibility Product Model Configuration Switch ASIC CPU 100G Switch Portfolio AS7726-32X ( DCS204) 32 x 100G Trident 3× 7 Intel x86 100G Switch Portfolio AS7712-32X ( DCS501) 32 x 100G Tomahawk Intel x86 100G Switch Portfolio AS7816-64X ( DCS500) 64 x 100G Tomahawk 2 Intel x86 40G Switch Portfolio AS6701-32X 32 x 40G Trident II Power PC 40G Switch Portfolio AS6712-32X 32 x 40G Trident II Intel x86 40G Switch Portfolio AS6812-32X 32 x 40G Trident II+ Intel x86 25G Switch Portfolio AS7326-56X ( DCS203) 48 x 25G 8x 100G Trident 3× 7 Intel x86 25G Switch Portfolio AS7312-54XS 48 x 25G 6 x 100G Tomahawk + Intel x86 10G Switch Portfolio AS5835-54T ( DCS209) 48 x 10G- T 6 x 100G Trident III Intel x86 10G Switch Portfolio AS5835-54X ( DCS208) 48 x 10G 6 x 100G Trident III Intel x86 10G Switch Portfolio AS5812-54T 48 x 10G- T 6 x 40G Trident II+ Intel x86 10G Switch Portfolio AS5812-54X 48 x 10G 6 x 40G Trident II+ Intel x86 10G Switch Portfolio AS5712-54X 48 x 10G 6 x 40G Trident II Intel x86 10G Switch Portfolio AS5600-52X 48 x 10G 4 x 40G Trident+ Intel x86 Multi- Gig Switch Portfolio AS4630-54NPE ( EPS203) 36 x 1/2.5G PoE 12 x 1/2.5/5/10G PoE Trident III Intel x86 1G Switch Portfolio AS4630-54PE ( EPS202) 48 x 1G PoE 4 x 25G Trident III Intel x86 1G Switch Portfolio AS4630-54TE ( EPS201) 48 x 1G 4 x 25G Trident III Intel x86 1G Switch Portfolio AS4610-54P 48 x 1G PoE 4 x 10G Helix4 ARM Cortex A9 1G Switch Portfolio AS4610-30P 24 x 1G PoE 4 x 10G Helix4 ARM Cortex A9 1G Switch Portfolio AS4610-54T 48 x 1G- T 4 x 10G Helix4 ARM Cortex A9 1G Switch Portfolio AS4610-30T 24 x 1G- T 4 x 10G Helix4 ARM Cortex A9 1G Switch Portfolio AS4625-54P 48 x 1G POE 6 x 10G Trident3-X2 Intel x86 1G Switch Portfolio AS4625-54T 48 x 1G-T 6 x 10G Trident3-X2 Intel x86 DELL Hardware Compatibility Product Model Configuration Switch ASIC CPU 100 G Switch Portfolio Z9264F- ON 64 x 100G Tomahawk 2 Intel x86 100 G Switch Portfolio S5232F-ON 32 x 100G Trident 3×7 Intel x86 100G Switch Portfolio Z9100- ON 32 x 100G Tomahawk Intel x86 25G Switch Portfolio S5296F-ON 96 x 25G 8 x 100G Trident 3× 7 Intel x86 25G Switch Portfolio S5248F-ON 48 x 25G 8 x 100G Trident 3× 7 Intel x86 25G Switch Portfolio S5224F-ON 12 x 25G 4 x 100G Trident 3×5 Intel x86 25G Switch Portfolio S5212F-ON 12 x 25G 3 x 100G Trident 3×5 Intel x86 10G Switch Portfolio S4048- ON 48 x 10G 6 x 40G Trident II Intel x86 10G Switch Portfolio S4148T-ON 48 x 10GBASE- T 2 x 40G 4 x 100G Maverick Intel x86 10G Switch Portfolio S4148F-ON 48 x 10G 2 x 40G 4 x 100G Maverick Intel x86 10G Switch Portfolio S4128F-ON 28 x 10G 2 x 100G Maverick Intel x86 1 G Switch Portfolio N3248P-ON 48 x 1G 30W PoE 4 x 10G Trident 3×3 Intel x86 1 G Switch Portfolio N3248TE-ON 48 x 1G 4 x 10G Trident 3×3 Intel x86 1 G Switch Portfolio N3224P-ON 24 x 1G 30W PoE 4 x 1 0 G Trident 3×3 Intel x86 1 G Switch Portfolio N3224T-ON 24 x 1G 4 x 10G Trident 3×3 Intel x86 1 G Switch Portfolio N3224F-ON 24 x 1G SFP 4 x 10 G Trident 3×3 Intel x86 1 G Switch Portfolio N3024ET-ON 24 x 1G 4 x 10G Helix4 ARM Cortex A9 Product Model Configuration Switch ASIC CPU 1 G Switch Portfolio N3024EP-ON 24 x 1G PoE 4 x 10G Helix4 ARM Cortex A9 1 G Switch Portfolio N3048ET-ON 48 x 1G 4 x 10G Helix4 ARM Cortex A9 Multi- Gig Switch Portfolio N3248 PXE- ON 48 x 1/ 2.5/ 5/10G 90W PoE 4 x 25G Trident 3×5 Intel x86 Multi- Gig Switch Portfolio N3224PX-ON 24 x 1/2.5/ 5/10G PoE 90W PoE 4 x 25 G Trident 3×3 Intel x86 Multi- Gig Switch Portfolio N3208PX-ON 4 x 1/2.5/5G PoE 4 x 1G PoE 2 x 10G SFP+ Hurricane 3 MG Intel x86 Multi- Gig Switch Portfolio N3132PX-ON 24 x 1G PoE 8 x 1/2.5/5G PoE 4 x 10G Firebolt 4 FS ARM Cortex A9 Multi- Gig Switch Portfolio N2248PX-ON 48 x 1G/2.5G 30W/60W PoE 4 x 25G Hurricane 3 MG Intel x86 Multi- Gig Switch Portfolio N2224PX-ON 24 x 1G/2.5G 30W/60W PoE 4 x 25G Hurricane 3 MG Intel x86 Multi- Gig Switch Portfolio N3248X-ON 48 x 1/ 2.5/ 5/10G 4 x 25G Trident 3×3 Intel x86 Multi- Gig Switch Portfolio N2248X-ON 48 x 1G/2.5G 4 x 25G Hurricane 3 MG Intel x86 Multi- Gig Switch Portfolio N2224X-ON 24 x 1G/2.5G 4 x 25G Hurricane 3 MG Intel x86 DELTA Hardware Compatibility Product Model Configuration Switch ASIC CPU 100G Switch Portfolio AG9032v 1 32 x 100G Tomahawk Intel x86 25G Switch Portfolio (controlled release) AG5648 v 1-R 48 x 25G Tomahawk + Intel x86 10G Switch Portfolio (controlled release) AG7648 48 x 10G Trident II Intel x86

Apr 03, 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

Pica8 Technote Automate NAC Configurations

Nov 29, 2024 - For details, please click the attachment icon below to view or download for a good reading experience or resources.