Addressed Issues in Prisma SD-WAN ION Device Release 5.5.5

The following table lists the issues addressed in Prisma SD-WAN ION Device Release 5.5.5.
Issue ID
Resolved an issue where the LAN side FIB had no prefixes present even though the LAN interfaces were Admin Up and had learned or configured prefixes present.
Resolved an issue where data center ION devices that have internet access via the internet labeled ports only fail to establish remote access sessions.
Resolved a rare issue where, Gmail traffic was improperly reclassified as SSL mid-flow and depending on path and security policy settings could result in the flow being dropped.
Resolved an issue where the web interface was showing Layer 3 LAN forwarding configured, but not configured on the ION device, while the LAN interfaces are configured as Layer 3 on the ION device.
Resolved an issue where the ION device did not forward traffic after a critical process was restarted.
Resolved an issue where a custom L4 application was improperly placed in the wrong QoS queue.
Resolved an issue when running both DHCP Server and DHCP relay on the same interface at a Prisma SD-WAN Branch causing the DHCP server to stop working.
Resolved an issue where, if a branch is in an L2 deployment model using bypass pairs, and 2 static routes are configured to 2 different next-hops in the same LAN network, incorrectly the next hop with the higher AD is programmed in the bypass pair FIB.
Resolved a rare issue where, after the elem-mgr process restarts it does not recover properly.

Recommended For You