Thursday, 31 July 2014
PRTG Trial version monthly migration.
PRTG NETWORK MONITORING TOOLS
PRTG Networking Monitoring Tools are the monitoring tools for vmware, mysql server ,windows server and linux platform server.
After download you must be key in your email address to gain the trail key from the website and in yours email address.
You will receive a mail in your mail account.Example as below.
Install Process
Setup a windows platform, and then double click the PRTG.exe file and keep pressing next for installation.
After install you will be have the file like below in START.
By the way do not need to click anything on it.
Open your Browser and key in yours PRTG server IP.
Will be automatic redirect to example below.
First time you can use following credential to login
Login name: prtgadmin
Password: prtgadmin
After login will same as this picture shown.
Press Run Configuration GURU.
Then press Start GURU.
After that will be like picture shown
Setup your account and changes your password.
Then save and next.
Go to Enter SNMP Credentials, and changes the string and port related to your monitor server.
Like our server are using xxxxxxxx and 161 snmp default port.
Then proceed to Monitor Your internet connection.
Key in yours default gateway and Dns server you are using.
Then go to the last one you are done Tab.
Then click on view my new sensor.
Then for sure you can saw these thing first
Other please made some research on it see how how add a group for other devices.
Remote probe Side
Connected to the probe you want to monitor
Allow port in iptables for the server.
/sbin/iptables -A INPUT -p udp -m udp --dport 161 -j ACCEPT #snmp
snmpd.conf
vi/etc/snmp/snmpd.conf
Replace as below
# First, map the community name "public" into a "security name"
# sec.name source community
com2sec notConfigUser default public
####
# Second, map the security name into a group name:
# groupName securityModel securityName
group Group v1 notConfigUser
group Group v2c notConfigUser
####
# Third, create a view for us to let the group have rights to:
# Make at least snmpwalk -v 1 localhost -c public system fast again.
# name incl/excl subtree mask(optional)
#view systemview included .1.3.6.1.2.1.1
#view systemview included .1.3.6.1.2.1.25.1.1
view all included .1
####
# Finally, grant the group read-only access to the systemview view.
# group context sec.model sec.level prefix read write notif
access Group "" any noauth exact all all none
Server side are completely setup.
Data migration on trial version
Migration Step by Step
In order to migrate an installation from a source computer to a target computer the following steps are necessary:
Step 1: Install PRTG on the target system
- Requires you to enter the license key and to activate the software. As long as the old installation is active this license will run as freeware.
Step 2: Stop core and probe services on source and target system
- Both systems: In the "PRTG Server Administrator" program choose the "Start/Stop" tab and click on "Stop Core Server"
- Both systems: In the "PRTG Probe Administrator" program choose the "Start/Stop" tab and click on "Stop Probe Service"
Step 3: Find the data folders
- Both systems: In the "PRTG Server Administrator" program choose the “Core Server” tab and click on "Local Storage of Data Files and Monitoring Database"
Step 4: Copy all files to the data folders of the target system
- Overwrite all files on the target system
- Note: The following folders are not necessary for the migration:
- Configuration Auto-Backups
- Logs (System)
- Logs (Debug)
- Logs (Web Server)
- Report PDFs Consider copying the Monitoring-Database Folder prior to starting the entire move, depending on the number of sensors the Monitoring Database could be quite large and so the copy-process could take quite a while.
Step 5: Export settings of the old core server and local probe from the Windows registry to a file
Warning: Please make sure you have a proper system backup before manipulating the Windows registry!
Note: If you migrate PRTG from a 32bit to a 64bit Windows, the following instructions will not work. Please see Step 6a in this case.
- On the old system, open the Windows registry editor and navigate to the PRTG registry key. The exact location varies, depending on the Windows operating system installed (32bit vs. 64bit).
- 32bit:HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor
- 64bit:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor
- Right-click on PRTG Network Monitor and Export the selected branch to a *.reg file. Save the file to a USB stick or network share.
- Note: The new PRTG server will use the same IP address as your existing server. Please make sure the new server actually owns the old IP addresses, and shut down the old server. If you need to change the IP address during migration, so the new server owns a different IP address, please follow the additional notes in the “After Migration” section below.
Step 6: Import settings of the old core server and local probe to the registry of the new server
Warning: Please make sure you have a proper system backup before manipulating the Windows registry!
Note: If you migrate PRTG from a 32bit to a 64bit Windows, the following instructions will not work. Please see Step 6a in this case.
- On the new system, make sure the installed Windows version matches the one of the old system, regarding the bit version. That means, if the old system ran a 32bit Windows, make sure that the Windows version on the new server is 32bit, too. Or 64bit, accordingly.Note: If you want to import settings from a 32bit Windows to a 64bit Windows version (or vice versa), please change the branch of the registry settings manually; we do not officially support this procedure.
- Import the PRTG settings to the Windows registry of the new server, for example, by double-clicking the *.reg file you exported on the old server.
- Note: The new PRTG server will use the same IP address as your existing server. Please make sure the new server actually owns the old IP addresses, and shut down the old server. If you need to change the IP address during migration, so the new server owns a different IP address, please follow the additional notes in the “After Migration” section below.
Step 6a: Migrating PRTG from 32bit to 64bit Systems
If you move your PRTG installation from a 32bit Windows to a 64bit Windows, registry export and import as described in steps 5 and 6 will not work. You have to copy the settings manually:
- Open PRTG Server Administrator on both the source (old) and the target (new) system.
- Open PRTG Probe Administrator on both the source and the target system.
- Manually transfer the settings from the source to the target system.
- Ensure that you copy all settings!
Please go on with Step 7.
Step 7: Only When Using Remote Probes: Check Core Server Settings
On the target system, please open the "PRTG Server Administrator" program. In the Core Server tab, make sure the settings for Probe Connection Management are correct: If you use Remote Probes, this setting must not be set to the first (default) option, but you must allow connections from remote probes; either on all IPs, or on specific IPs you define here.
Note: This step is necessary, because the import of registry settings does not always work flawlessly here, depending on the Windows version used.
Step 8: Check Data Path
On the target system, please open the "PRTG Server Administrator" program. In the Core Server tab, make sure the folder for Local Storage of Data Files and Monitoring Databasematches the path you copied the data to (in Step 4). Change the setting to the correct path, if necessary.
Step 9 (optional): Adjust settings of existing Remote Probe installations
- This step is only necessary if your PRTG configuration uses Remote Probes and if the IP address of the core server changes during this migration
- Connect to each Remote Probe system, open the "PRTG Probe Administrator" program and enter the new IP address of the target server
- You might also need to change settings in the PRTG web interface so your new installation accepts incoming remote probe connections (on all IP addresses, if applicable). Please change settings under Setup | System Administration | Core & Probes.
Step 10: Start core and probe services on the target system
- Target system: In the "PRTG Server Administrator" program choose the "Start/Stop" tab and click on "Start Core Server"
- Target system: In the "PRTG Probe Administrator" program choose the "Start/Stop" tab and click on "Start Probe Service"
Step 11: Log into the web interface and review monitoring setup and results
- Check if the migration was successful.
Step 12 (optional): Update to the latest version of PRTG
- We recommend you always keep your systems up to date.
After Migration
After a migration you may need to look at the following aspects, depending on your configuration.
If the IP Address of the Server Has Changed
- The PRTG core server automatically switched its web server to “localhost”. In order to make the web interface available again under the IP address of the core server, please open the “PRTG Server Administrator” and change settings in the “Web Server” tab accordingly.
- If the IP address of the server changed you may need to change firewall settings and/or NAT settings which apply to the old address
- If you use a SMTP relay server for email delivery out of PRTG you may need to allow relaying for the new IP address
- When running a PRTG cluster: If the IP address of the server changed, please open the PRTG web interface of the Master node and navigate to Setup | System Administration | Cluster.
- If you moved a Master node: Change the IP address entry of the master node, so existing Failover nodes are able to re-connect to the new server.
- If you moved a Failover node: Change the IP address entry of the failover node, so the Master node is able to re-connect to the new failover server.
If the Hostname of the Server Has Changed
- Please navigate to Setup | System Administration | User Interface ("System & Website" in previous versions) and check the DNS Name field. Make sure you enter the same DNS Name you used before, so all existing links to public Maps and all connections configured in clients' Enterprise Consoles continue working.
- If relevant in your network, you should go to the Notification Delivery tab and check theHELO Ident field. Make sure it uses a value that is accepted by your mail server.
Other Aspects
Источник: http://linuxtopsupport.blogspot.com/2014/07/prtg-trial-version-monthly-migration.html | 
