All of the sensor configuration is stored on the EMS and pushed to the
sensor during a "deploy" operation; that is to say, aside from basic network
settings, there is nothing worth saving. So, this might be a good
opportunity to install the latest Dragon ISO on all sensors. During this
process the setup script will be run. Remember to have the basic networking
parameters (hostname, IP, mask, gateway) and the shared-secret for the new
EMS ready before you begin.
If, for whatever reason, you want to preserve the current version of ISO and
dragon application, I would recommend that you remove or rename the dragon
installation directory and re-run the install.
Our GTAC is available to walk you through the process if you have any
concerns or questions.
Regards,
Patrick Bosa | Director, Engineering
Enterasys Networks
Office: +1.603.952.5812 | Cell: +1.978.494.2107
Email: ***@enterasys.com
-----Original Message-----
From: Tom Keren [mailto:***@gmail.com]
Sent: Thursday, June 20, 2013 9:50 AM
To: Enterasys Customer Mailing List
Subject: [enterasys] Pointing the Dragon Sensor to another EMS Server
I am currently involved in a project where we are going to point all of our
Dragon Sensors to a completely new EMS Server. What is the best methodology
for doing this? Should we rerun the setup script on the sensors themselves?
Will that wipe the configuration on the sensors clean? (Which is not an
issue)
---
To unsubscribe from enterasys, send email to ***@unc.edu with the body:
unsubscribe enterasys ***@enterasys.com
---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org