These notes summarizes PICOS 4.1 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.
Layer 2 and Layer 3
DHCPv6 relay is the IPv6 equivalent of the DHCP relay for IPv4. The DHCPv6 relay agent passes DHCPv6 solicitation or request to the DHCPv6 server on a different subnet and get the returned DHCPv6 advertise or reply from the DHCPv6 server back to the DHCPv6 client.
Support OSPFv3 for IPv6
OSPFv3 (Open Shortest Path First version 3) is added to support IPv6. Please note that VRF over OSPFv3 is not available in this version (4.1.0).
Multiple OSPF Instances
Eight OSPF processes are started if multi-instance is enabled. Each OSPF instance, identified by an unique number (1 - 8), can be configured separately. Please note that multiple OSPF instances are supported only in the default VRF with OSPFv2.
Support VRRPv3 for IPv6
VRRPv3, with IPv6 introduced, can bundle 2 physical PICOS routers as one single virtual router. The ND (Neighbor Discovery) protocol is enabled on the virtual IPv6 VRRP interfaces by default. In particular, the RA (Router Advertisement) packets will be sent out from the VRRP virtual interfaces periodically.
Update ping and traceroute for IPv6
With upgrade to Debian 10.9, CLI commands, ping and traceroute, are updated to support IPv6. And ping6 and traceroute6, are removed from CLI under operational mode.
Added the support of multi-line banners with the newly-added CLI command "set system login multiline-banner ...".
Layer 2 and Layer 3
DNS name-server and DNS Search List
If users configure DNS name-server or DNS search list from PICOS CLI, the associate configuration included in /etc/resolv.conf should not be updated from DHCP server.
Cannot Access to SNMP Agent
If users enable management VRF and Inband connection as following CLI commands, SNMP agent stopped responding.
The Size of NETCONF.events Increases without Limit
If users configure NETCONF on the switch, the size of NETCONF log file /tmp/stream/NETCONF.events will increase without limit. Add a mechanism of rotation to fix this issue. Keep the size of this file within 2M.
Crash if Users Configure port-mode via NETCONF
The NETCONF process might crash if configure port-mode to "trunk" and then back to "access" repeatedly via NETCONF.
Multiple Output Tunnel Ports in a VXLAN Flow
Multiple tunnel ports can be added as the output ports in a VXLAN flow. It requires that the VXLAN ports must have the same VNI (Virtual Network Identifier) on the ingress side.