These notes summarizes PICOS 3.8 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.
New Features
Layer 2 and Layer 3
Bug ID | Release | Description |
---|---|---|
12814 | 3.8.0 | VXLAN Routing |
13098 | 3.8.0 | Enable VXLAN on NAC Ports |
13101 | 3.8.0 | DNS Domain Search List |
Hardware
Bug ID | Release | Description |
---|---|---|
12496 | 3.8.0 | Support AS5835-54T |
Fixed Issues
Layer 2 and Layer 3 Features
Bug ID | Release | Description |
---|---|---|
13106 | 3.8.0 | Cannot Read out EEPROM Data on AS7326-56X |
13172 | 3.8.0.1 | Aquantia PHY Firmware is Not in SPI Flash on N3224PX-ON Ports cannot link up if Aquantia firmware is not loaded to the RAM of the external PHY on N3224PX-ON. In case that Aquantia PHY firmware is not in SPI flash attached to the external PHY, PICOS will get CLD image of Aquantia PHY firmware programmed into the SPI flash. And then reset the external PHY to load Aquantia PHY firmware and make ports up automatically. |
13171 | 3.8.0.1 | Cannot Forward Traffic if Link Speed is 5G on N3224PX-ON If link speed is negotiated to 5G with a connected device, the traffic from the attached device cannot be forwarded. This issue was fixed in 3.8.0.1. |
13161 | 3.8.0.1 | Cannot Recognize PoE Device of Class 4-8 on N3224PX-ON By testing with PoE tester, PD class 4-8 cannot be recognized on N3224PX-ON. This issue was fixed in 3.8.0.1. |
13173 | 3.8.0.1 | NAC: Downloadable ACL Rules with L4 Port Range don't Work on Trident3-X3 Platforms A DACL rules to match a L4 port range cannot be applied to the ASIC hardware on Trident3-X3 Platforms such as Dell N32XX and EdgeCore AS4630. This issue was fixed in 3.8.0.1. |
13159 | 3.8.0.1 | PoE Cannot Work on N3132PX-ON PoE cannot work on specific port randomly on N3132PX-ON. This issue was fixed in 3.8.0.1. |
OVS Features
Bug ID | Release | Description |
---|---|---|
13150 | 3.8.0 | OVS Web Service is Still up Even If It is Disabled in PICOS Configuration The lighttpd service is brought up by systemd because the setting of the option "WantedBy" in lighttpd.service, which walks around the toggle option (ovs_enable_lighttpd=false) in /etc/picos/picos_start.conf. |