If a failover occurs from the primary to secondary local director, what is the state of the config on the newly active standby device. During normal operation, I believe the standby device only stores the config in memory. Does this mean that if it is rebooted after it has taken over from the failed primary, the config is lost? What is the recommendation regarding safeguarding the config on the standby active device whilst the primary is being attended to?
As you mentioned, when the standby takes over the configuration is stored in the memory and the previous configuration on the standby is erased. There is a bug with the local director not replicating its configuration to the standby unit correctly.
That's probably the reason why the standby might have rebooted. I have no idea on how to safeguard the configuration. Any suggestions out there??
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...