This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Training, Documentation, & General Discussions
- FAQs
- NetSight - Moving the NetSight Server to a New Sys...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
NetSight - Moving the NetSight Server to a New System
NetSight - Moving the NetSight Server to a New System
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
09-04-2013 11:01 PM
Article ID: 13209
Products
NetSight Console
NetSight Inventory Manager
NetSight Policy Manager
NetSight Automated Security Manager
NetSight NAC Manager
Goals
Move the NetSight server from one system to another.
Solution
***USER INFORMATION***
If you are authenticating your NetSight users with the domain as opposed to the local system then that should not be an issue. If you are authentication to the local system then you will need to make some user additions to NetSight to reflect the new system name (unless the system name will be exactly the same then no changes will be needed). If you do need to make additional users then you can use the following procedure:
1. Select Tool -> Authorization/Device Access
2. Make sure that the Users/Groups tab is selected.
3. Click on the Add User button to add the new user information.
**NOTE** this step is not needed with 3.2.x and higher as the user you are already logged in as will be added to that database during the restore process.
***DATABASE***
To move the database to the new system it's as easy as doing a backup on the original system, moving the database file and the InventoryMgr directory that gets created to the new system and then restoring that database. This can be done using the following procedure.
1. Select Tools -> Server Information -> Database.
2. Click on the Backup button and make note of the location where that will be saved.
3. Move the entire contents of that saved directory to the new system.
Note that there will be a database file and an InventoryMgr directory if you have archived configs or created any config templates. Both need to be moved over.
Use the same procedure above to Restore the database on the new system (select the Restore button as opposed to the Backup button).
***TRAPS AND SYSLOG***
If the IP address of the new system will be different then you may need to adjust the trap and syslog receivers on the network devices. If you are not using traps or syslog then there is no need to do this. If the IP address is the same then there is also no need to worry about this. If changes need to be made then the following tech notes can be used:
9924 Using NetSight to setup syslog on devices
9923 Using NetSight to setup traps and informs on devices
If you were using SNMPv3 traps/informs then you will want the following files as well:
\NetSight\appdata\snmptrapd.conf (contains all your switch information for traps and inform messages)
\NetSight\services\snmptrapd.conf (contains the engineID that is configured on the switches for informs)
If you have modified the trap definition file you will want to move the following file to the server:
\NetSight\services\trapd.conf
Stop the NetSight services (make sure trap service is stopped as well). Replace rename the current files and then replace with the ones from the original system. Restart the services for the changes to take.
***FLEXVIEWS***
If any custom FlexViews were made then you will want to move those over as well. Any FlexView that was stored on the Server (would have needed to be manually copied to the server as they are normally stored on the client system) would have been placed into the following directory (or subdirectories) so that they could be distributed to all the clients:
C:\Program Files\Enterasys Networks\NetSight\appdata\System\FlexViews (normally stored in the MyFlexViews folder, but could be located in any place)
***MIBS***
If you have imported any third party MIBs into NetSight then you will need to re-add those to the new server. Third party MIBs are usually added to the following directories on the server:
\NetSight\appdata\System\mibs\MyMibs
or
\NetSight\appdata\System\mibs\thirdparty
***SCRIPTS***
If you have configured any scripts for ASM or Alarm Tools you will want to move those to the new system. These are located in the following directory on the NetSight server:
\NetSight\scripts
***REHOST LICENSE***
To rehost the license key you could either do the following or you can send me the old MAC of the system and the MAC of the new system.
Use the following procedure to rehost a license:
1. Log into the Enterasys Extranet site.
2. Select My Enterasys -> My Licenses menu pick.
3. Select the My Licenses link.
4. Click on the link that is the entitlement for the NetSight Console.
5. Select Manage Licenses link.
6. Place a check in the line item for the NetSight Console activationID.
7. Click on the Rehost button.
8. Enter the new MAC address without any separators -- i.e. 00001122334455
9. Click on the Rehost button in the lower right.
Products
NetSight Console
NetSight Inventory Manager
NetSight Policy Manager
NetSight Automated Security Manager
NetSight NAC Manager
Goals
Move the NetSight server from one system to another.
Solution
***USER INFORMATION***
If you are authenticating your NetSight users with the domain as opposed to the local system then that should not be an issue. If you are authentication to the local system then you will need to make some user additions to NetSight to reflect the new system name (unless the system name will be exactly the same then no changes will be needed). If you do need to make additional users then you can use the following procedure:
1. Select Tool -> Authorization/Device Access
2. Make sure that the Users/Groups tab is selected.
3. Click on the Add User button to add the new user information.
**NOTE** this step is not needed with 3.2.x and higher as the user you are already logged in as will be added to that database during the restore process.
***DATABASE***
To move the database to the new system it's as easy as doing a backup on the original system, moving the database file and the InventoryMgr directory that gets created to the new system and then restoring that database. This can be done using the following procedure.
1. Select Tools -> Server Information -> Database.
2. Click on the Backup button and make note of the location where that will be saved.
3. Move the entire contents of that saved directory to the new system.
Note that there will be a database file and an InventoryMgr directory if you have archived configs or created any config templates. Both need to be moved over.
Use the same procedure above to Restore the database on the new system (select the Restore button as opposed to the Backup button).
***TRAPS AND SYSLOG***
If the IP address of the new system will be different then you may need to adjust the trap and syslog receivers on the network devices. If you are not using traps or syslog then there is no need to do this. If the IP address is the same then there is also no need to worry about this. If changes need to be made then the following tech notes can be used:
9924 Using NetSight to setup syslog on devices
9923 Using NetSight to setup traps and informs on devices
If you were using SNMPv3 traps/informs then you will want the following files as well:
\NetSight\appdata\snmptrapd.conf (contains all your switch information for traps and inform messages)
\NetSight\services\snmptrapd.conf (contains the engineID that is configured on the switches for informs)
If you have modified the trap definition file you will want to move the following file to the server:
\NetSight\services\trapd.conf
Stop the NetSight services (make sure trap service is stopped as well). Replace rename the current files and then replace with the ones from the original system. Restart the services for the changes to take.
***FLEXVIEWS***
If any custom FlexViews were made then you will want to move those over as well. Any FlexView that was stored on the Server (would have needed to be manually copied to the server as they are normally stored on the client system) would have been placed into the following directory (or subdirectories) so that they could be distributed to all the clients:
C:\Program Files\Enterasys Networks\NetSight\appdata\System\FlexViews (normally stored in the MyFlexViews folder, but could be located in any place)
***MIBS***
If you have imported any third party MIBs into NetSight then you will need to re-add those to the new server. Third party MIBs are usually added to the following directories on the server:
\NetSight\appdata\System\mibs\MyMibs
or
\NetSight\appdata\System\mibs\thirdparty
***SCRIPTS***
If you have configured any scripts for ASM or Alarm Tools you will want to move those to the new system. These are located in the following directory on the NetSight server:
\NetSight\scripts
***REHOST LICENSE***
To rehost the license key you could either do the following or you can send me the old MAC of the system and the MAC of the new system.
Use the following procedure to rehost a license:
1. Log into the Enterasys Extranet site.
2. Select My Enterasys -> My Licenses menu pick.
3. Select the My Licenses link.
4. Click on the link that is the entitlement for the NetSight Console.
5. Select Manage Licenses link.
6. Place a check in the line item for the NetSight Console activationID.
7. Click on the Rehost button.
8. Enter the new MAC address without any separators -- i.e. 00001122334455
9. Click on the Rehost button in the lower right.
0 REPLIES 0
