![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1662213.1 : Oracle ZFS Storage Appliance: Dynamic routes created on the appliance are not flushed as expected
Dynamic Routing describes the capability of a system, through which routes are characterized by their destination, to alter the path that the route takes through the system in response to a change in conditions. In short, the location of the remote resource is decided at run time. The adaptation is intended to allow as many routes as possible to remain valid (that is, have destinations that can be reached) in response to the change. The appliance supports both RIPv1 and RIPv2 for IPv4, and RIPng for IPv6. Routes that are configured via these protocols are marked as type "dynamic" in the routing table. Accordingly, disabling this service will cause all dynamic routes to be removed from the routing table. RIP and RIPng listen on UDP ports 520 and 521 respectively. As such, the appliance is supposed to be updating the routing table dynamically at run time. In this Document
Created from <SR 3-8530349403> Applies to:Sun ZFS Storage 7120 - Version All Versions to All Versions [Release All Releases]Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases] Sun Storage 7310 Unified Storage System - Version All Versions to All Versions [Release All Releases] Sun Storage 7210 Unified Storage System - Version All Versions to All Versions [Release All Releases] Sun Storage 7410 Unified Storage System - Version All Versions to All Versions [Release All Releases] 7000 Appliance OS (Fishworks) SymptomsWith releases prior to 2011.04.24.8.1,1-2.44.3.5 and ak-2013.06.05.1.8, it was found that dynamic routes were not getting flushed. Routes that in.routed had received through RIP and have been installed in the kernel are supposed to be automatically removed if they are no longer being received through RIP. This resulted in duplicate entries in the routing table as well as previously broadcasted routes which were no longer applicable, continued to remain in the routing table. This would result in clients not able to communicate with the appliance and messages like the following in /var/ak/logs/debug.sys May 2 20:47:01 xxxx in.routed[2209]: [ID 464608 daemon.error] route X.X.X.0/24 --> X.X.X.X nexthop is not directly connected
CauseThis is a known issue/bug - now fixed in later Appliance Firmware Releases. <Internal> BUG 17547330 - 15530952 needs more work. in.routed not deleting routes </Internal> SolutionThe problem is resolved by upgrading to Appliance Firmware Release 2013.1.2.0, 2013.1.1.9 or (future) Appliance Firmware Release 2011.1.10.0 References<BUG:17547330> - 15530952 NEEDS MORE WORK. IN.ROUTED NOT DELETING ROUTESAttachments This solution has no attachment |
||||||||||||||||||
|