No further explanation was offered, no. Note, the security concern point did come to me second-hand. The support tech I was working with said that was what he'd been told by either the engineer group behind NCM, or the guys that handle the modeling gateway. I assumed it was a weak reference to the configs having unmasked password information and such, but I felt like that was a bit of a non-issue, considering (as you also mention) the exported config files do contain the raw configs, with unmasked password data, if you enable that function.
-- Christopher Cashell -----Original Message----- From: Bohra, Saurabh [mailto:[email protected]] Sent: Tuesday, February 28, 2012 6:15 PM To: Cashell, Christopher P.; spectrum ([email protected]) Subject: RE: [spectrum] configs history export Chris, Did support give you any explanation what will be the security concern in transferring config history? If the product allows you to export all the config files on the server, isn't that same security risk as having the config in an XML file... Saurabh Bohra O: 860-766-0842 | M: 860-385-3597 | e-mail: [email protected] -----Original Message----- From: Cashell, Christopher P. [mailto:[email protected]] Sent: Tuesday, February 28, 2012 12:09 PM To: spectrum Cc: spectrum Subject: RE: [spectrum] configs history export We just went through this exact scenario, and I opened a case with support to figure out how to accomplish it. What we were told is that we were basically screwed, and there was no way to do it. The config history is not an exportable object for the modeling gateway, and according to support, one of the main reasons they don't support exporting it due to "security concerns". I did open a feature request to get this added, but I'm not holding my breath. The best work-around we were able to come up with is to export the devices and model them on the new landscape, but don't delete the old ones. Instead, put them in maintenance with a Note specifying that they'd been migrated. Then, after the new model has been in place for a couple of months and built up some configuration history, we're going to go back and remove the old models. We also enabled the config dump to the filesystem for each of our Spectrum servers (Explorer->Configuration Manager->Information->Export Configuration). We set that up to dump every unique configuration to $SPECHOME/config/ at each change, so we could maintain our own long term config history. (Note, this would also be mitigated to a large extent if Spectrum had a concept of "retired" devices, so you could minimize resources used on a device, while still retaining historical information on it such as config history. I opened an enhancement request on that, too, but don't expect it anytime soon.) -- Christopher Cashell -----Original Message----- From: javi [mailto:[email protected]] Sent: Tuesday, February 28, 2012 4:21 AM To: spectrum Subject: [spectrum] configs history export Hallo list We want to split the spectrum db, because we have too many objects and the application is becoming overloaded. The server has still enough resources. I've configured the gateway tool to export some containers and to import them in another server, that will have another landscape id. The only problems is that the gateway exports no config at all. We want to export the whole config history each device but we don't know how. I would appreciate any idea. Thank you and kind regards Javier --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] Please consider the environment before printing this e-mail. --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
