Changing the IP address of vSCOUT: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
== Introduction == | == Introduction == | ||
When the IP address of the host where | When the IP address of the host where vScout is running on changes, how does this affect vScout and the nGeniusONE server's device configuration? | ||
| | ||
| Line 8: | Line 8: | ||
== Solution == | == Solution == | ||
The link between nGeniusONE Server and vScout depends on its serial number, not its IP address. | |||
Reboot the host after the change and nGeniusONE Server will update its proper configuration. You can monitor the change in module Device Configuration > Devices. | |||
You may have to adjust the packet forwarding filter in Device Configuration > Devices > Traffic Forwarding to reflect the | Keep in mind that, although the service may start quickly, it could take several minutes before vScout collected data is visible in nGeniusONE. | ||
You may have to adjust the vScout's packet forwarding filter in Device Configuration > Devices > Traffic Forwarding to reflect the change of the IP address of the host. | |||
Latest revision as of 18:59, 6 November 2018
Introduction
When the IP address of the host where vScout is running on changes, how does this affect vScout and the nGeniusONE server's device configuration?
Solution
The link between nGeniusONE Server and vScout depends on its serial number, not its IP address.
Reboot the host after the change and nGeniusONE Server will update its proper configuration. You can monitor the change in module Device Configuration > Devices.
Keep in mind that, although the service may start quickly, it could take several minutes before vScout collected data is visible in nGeniusONE.
You may have to adjust the vScout's packet forwarding filter in Device Configuration > Devices > Traffic Forwarding to reflect the change of the IP address of the host.