T.R | Title | User | Personal Name | Date | Lines |
---|
2953.1 | | NETCAD::DOODY | Michael Doody | Fri Nov 03 1995 16:28 | 19 |
| It depends on what you mean by its "configuration".
It is safe to assume all 900 max modules save some configuration in
NVRAM (flash is usually for the firmware). The kinds of things stored
in the module's NVRAM are its IP address, trap addresses, netmask,
port address filters, and internal LAN port groupings in the case of a
PortSwitch repeater.
When a module is installed in a DEChub 900MS, it is the Hub that stores
the backplane configuration - which LANS are defined, what ports are
connected to what LANs, what is the LIGO set (like ethernet-front).
Now, this Hub configuration is stored in the Hub's NVRAM so that it
will survive power failures and such. However, the hub-related
configuration is deleted when the module is removed from the Hub while
the Hub is running. Except in the case of FDDI modules when FDDI
Auto-Healing is enabled. We're working to improve this for a future
release.
-Mike
|
2953.2 | | NETCAD::MILLBRANDT | answer mam | Fri Nov 03 1995 16:48 | 40 |
| For products available today, the answer is yes ONLY
if the customer uses clearVISN Resilience to save
entire hub configurations onto disk.
Other than that, the answer is no.
Module configurations will survive a power down or a
reset of any module or of the MAM, or both. Most
module configurations are not currently saved over
removal/insertion (but see auto-healing below).
Anything entered via the Setup console will be saved in
NVRAM and survives with the module, even if you stick in
on a shelf for a year and insert it in a different hub.
What other information is saved in NVRAM depends on the
module.
For information entered via Hubwatch, the best way to
save it is with the new clearVISN Resilience product
(which is even harder to spell than to pronounce). That
will save the configuration of an entire hub onto disk,
and you can reload a hub with that config at a later
time. This only has 'hub granularity', though. You
can't save and restore just the PORTswitch900CP in slot 3.
FDDI modules, and the DECswith900EF when using the FDDI
port, can also make use of Auto-Healing. If you remove
one of these modules, its LAN Interconnect configuration
is remembered and restored when a module of the same
type is reinserted.
For other modules, any information entered via the
LAN Interconnect display is not saved, including
the Ligo front/back states. There is probably other
info that doesn't survive, also, like port settings
on older 90 repeaters.
Dotsie
|
2953.3 | true, cannot save/restore single module's connections | NETCAD::MOWER | | Fri Nov 03 1995 17:50 | 17 |
|
> For information entered via Hubwatch, the best way to save it is with the
> new clearVISN Resilience product ... That will save the configuration of an
> entire hub onto disk, and you can reload a hub with that config at a later
> time. This only has 'hub granularity', though. You can't save and restore
> just the PORTswitch900CP in slot 3.
Just a clarification of the above comment from .-1...
clearVISN Resilience _can_ save/restore the configuration of a single
_module's_ settings. However, backplane configuration, (stored in the
hub), is saved/restored on an entire hub900 basis; (i.e. the hub
backplane configuration you save can only be restored to a hub that has
the same types of modules in exactly the same slots). It is not
possible to save/restore a specific module's hub backplane connections.
Carl.
|
2953.4 | | SCAS01::DAVIES | Mark, SCA Area Network Consultant | Mon Nov 06 1995 08:52 | 2 |
| Thanks.
|
2953.5 | It inconsistently varies. | PTOJJD::DANZAK | Pittsburgher � | Mon Nov 06 1995 09:34 | 11 |
| Note that "reset to factory" option in HUBwatch does not always seem to
do that....i.e. I still end up with connections pointed to the
backplane when in a hub.
We do need a paragraph in each modules user manual which describes
EXPLICITELY what is and is not reset when things are reset. Right now,
it's a crap shoot.
Regards,
j
|
2953.6 | Can TSM be used to save configs? | RTP4ME::GALLAGHER | Put me in coach! | Mon May 20 1996 10:06 | 14 |
|
I have a customer with a similar question specifically on a 900GM.
They want to know if a 900GM dies and must be replaced w/ one from
the box, can they use TSM to upload the config. from the old 900GM?
If so, is there a TSM version that supports the 32 ports?
Forgive my ignorance on the TSM product, but I know nothing about
it and am simply requesting info for the customer.
Any assistance would be greatly appreciated.
Thanks,
Ed Gallagher
|
2953.7 | | CSC32::D_PERRIN | | Mon May 20 1996 12:03 | 2 |
| TSM 2.1 supports the 900gm. -noted::tsm note 641
|