Port-channel recovery conflicts with UPT when port-channels are used as uplink (22120613)
Workaround — If a port-channel will be used as an uplink or downlink port, then the port-channel recovery feature must be disabled by running these commands at the SEFOS prompt:
configure terminal
set port-channel error-recovery-time 0
end
copy run startFS privilege feature for ES2-72 x86 platform (21810986)
Due to this fix, non-root local users do not get restored after an upgrade to 2.0.0.5.
Workaround — You must recreate the local users and assign the fs_privilege level explicitly.
No way to reset NTP back to default without a global reset (21240834)
Workaround — None.
SLB failover and fallback behavior discrepancy between IPv4 and IPv6 routes
Discrepancies in behavior during a failover or failback event are the result of changes to SLB in release 2.0.0.5 that fix certain SLB IPv6 related issues.
After a failover to a standby, if the standby server also goes down and no servers in the LBG are up, then the output of show slb shows all the IPv6 routes as cleared. The IPv6 routes, however, show as idle or failed.
Similarly, when the standby comes back up, the IPv4 routes show the state transition correctly, but IPv6 remains in the. same state and does not s how the routes completely
Currently there is no distinction between the behavior when a single link goes down versus when all the links go down in SLB IPv6. Similarly, when the single link comes back up, the state does not change until all the links are up.
This issue is related only to SLB IPv6. SLB IPv4 is not affected. This behavior also is seen when the servers are one hop away from the switch where SLB is configured, but not when the servers are connected directly to the switch.