ZEQUO 4600RE(PN36241L) Release Note December 13, 2023: Version 2.0.1.03 - Resolved Issues: 1)VLAN mapping settings for Private VLANs are not applied at reboot. 2)Unintended behavior occurs even though the Dynamic ARP Inspection function is disabled. -Interface on which you are configuring a port channel The initial value of the ARP reception rate upper limit (15pps) is applied, and any changed rate settings are also applied. -Interface on which you are not configuring a port channel The initial value of the ARP reception rate upper limit (15pps) is not applied, but the changed rate setting is applied. 3)After creating a file on an SD card using the backup machine of a stuck device and replacing it with an SD card that does not contain files, a file with the same file name cannot be created. February 7, 2023: Version 2.0.1.02 - Resolved Issues: 1) If this device with the IGMP function set receives an IGMP query packet from another device, a communication disconnection may occur. January 11, 2023: Version 2.0.1.01 - Resolved Issues: 1) Fixed an issue where communication of terminals that failed step authentication could not be blocked. 2) Fixed a problem that communication breakdown occurs when SSH connection is repeatedly continued to be executed. 3) Fixed a problem that "SSH Key verify error" may be displayed and connection may be refused when receiving a specific SSH connection request packet. 4) Fixed a problem that SSH connection may be disconnected while getting Log by SSH. 5) Fixed a problem in which packets with Checksum field of 0x0000 in ICMP messages were received but not responded. 6) Fixed a problem where the "vrrp track critical-ip" setting could be deleted after reboot. 7) Fixed a problem in which the link of one of the stacked ports may not be up when stacked devices are started up. 8) Fixed a problem in which an error would occur if a configuration file of a device other than the master device is saved to the SD card after the settings have been changed and saved in the stacked devices. 9) Fixed a problem in which deleting the loop history log of a stuck device would not restore the status LEDs of all devices except the master device from the state after loop detection. 10) Fixed a problem that stack-related Traps may not be sent properly when the master device is down. January 11, 2022: Version 2.0.0.11 - Specification Changes: 1)System log / SNMP trap issuance delay time setting command. logtrap linkchange delay <0-30> - Resolved Issues: 1)When the RRP status of the stacked device becomes complete, the wrong communication path may be learned. September 30, 2021: Version 2.0.0.10 - Resolved Issues: 1) If the RRP route-change occurs, the communication is not transferred to some IP addresses. If this failure occurs in the firmware version, which is earlier than 2.0.0.09, relearning ARP allows the communication to be transferred. 2) Despite that the connection condition of LLDP neighbor device is not changed,the log of "LLDP-MED Topology change detected" may become recorded. July 30, 2021: Version 2.0.0.09 - Resolved Issues: 1) The link-down rarely occurs regarding Ver.2.0.0.08. 2) Disconnections may occur if our device receives the specific HTTP communication when enabling the WEB authentication function. 3) The loop detection and blocking (or shut-off) function may operate on the port, where the link-aggregation is configured during the boot-up. 4) Disconnections may occur if neighboring devices cause the system down when using IP multicast routing. 5) Regarding the configuration file, which is saved into the main unit by copying the content of an SD card on the WEB settings screen, he file cannot be specified as the boot-up file. March 3, 2021: Version 2.0.0.08 - Specification Changes: 1) We added the command of "mac-address-table sync time". 2) We added the command of "show ipv4 ipfdb/show ipv6 ipfdb". - Resolved Issues: 1) We shortened the switching-time of the communication route, which is necessary, when the stack connection is deactivated. 2) When the stack connection becomes deactivated, the disconnection of communication occurs on a link-aggregation port. 3) The VLAN1 settings is not displayed in a configuration. 4) If a backup device of the stack becomes connected, responding normally to the communication for this deivce may become failure. 5) If a backup device of the stack becomes connected, OSPF processing may not be completed. 6) If you configure two or more RRP domains to change one status of the RRP domain to "disabled", other RRP domains do not operate (or work) normally. 7) You cannot specify the firmware for a boot-file from an SD card, on a WEB configuration interface. 8) The configuration of lldp management-address is not reflected. 9) Failure to configure lldp management-address, which is saved when you reboot. 10) We revised OID of the following SNMP traps ・vrrpTrapNewMaster ・vrrpTrapAuthFailure ・pimNeighborLoss ・pimInvalidRegister ・pimInvalidJoinPrune ・pimRPMappingChage ・pimInterfaceElection 11) When you execute "clear running-config", a MAC address that dynamically learns cannot be cleared. 12) In an environment of high communication-load, VRRP may not work normally. 13) When a master of VRRP operation device becomes switched, PBR information is not updated, and then the ommunication-route does not become switched. 14) When you connect a server through this stacked-device, packets whose destination is a virtual address of the Windows NLB unicast-mode cannot be transferred. 15) If an interface that transfers the MAC address data, which is statically registered on an ARP table, is a link-aggregation port, the communication does not work after the port becomes link-down/up. 16) If you change the interface VLAN mode after configuring a ring-protocol, the status of the ring-protocol becomes "Fail" and then a loop occurs. 17) If the communication-load is high on the same VLAN with the IP address used on an RRP master,the loop irregularly occurs. Octorver 1, 2019: Version 2.0.0.02 First release.