T.R | Title | User | Personal Name | Date | Lines |
---|
1231.1 | Basically yes | SSDEVO::RMCLEAN | | Thu Apr 10 1997 13:57 | 4 |
| In a word yes. The configuration information is saved any time that the
non-volitile memory is changed on that controller. It is not easy to describe
when the configuration changes but the goal is to preserve the state of
the nv memory.
|
1231.2 | ?? | GEM::SHERGOLD | We are 100% sure; well almost!! | Sun Apr 20 1997 01:34 | 4 |
| It seems an oxymoron to be talking about preserving the state of
"non-volitile" (sic) memory. Can you explain please?
Keith
|
1231.3 | Too busy?? | GEM::SHERGOLD | We are 100% sure; well almost!! | Sun Jun 01 1997 07:09 | 3 |
| Ah well! I guess you can't.
Keith
|
1231.4 | Very busy... | SSDEVO::RMCLEAN | | Mon Jun 02 1997 12:22 | 2 |
| Yup... You save NV because should you install a different controller you
might want that info restored to the new controller...
|
1231.5 | Note that Save_Config is NOT recommended for Dual-redundant controllers | SSDEVO::THOMPSON | Paul Thompson, Colorado Springs | Tue Jun 03 1997 10:23 | 2 |
| I believe that you will find in the release notes that use of the
SAVE_CONFIG option is not recommended in dual redundant configurations.
|
1231.6 | Yup that is true | SSDEVO::RMCLEAN | | Tue Jun 03 1997 12:00 | 3 |
| Yes that is true it is not recommended but it still works the same way.
The dual controllers can restore the configuration from the remaining
controller therefore they really don't need save configuration feature.
|