|Processor||IntraVUE has been designed to work with a low power computer|
|RAM (available)||2 GB: 250+ nodes, 4 GB: 500+ nodes, 6 GB: 1000+ nodes, 8 GB: 1500+ nodes|
|Disk space||4 GB: 500+ nodes), 8 GB: 1000+ nodes, 12 GB 1500+ nodes|
Windows Server 2000, 2003, and 2008; Windows XP Pro; Windows 7 32-bit and 64-bit, and Windows 10 / Server 2016. Windows Server 2012, Vista, and Windows 8 (and variants) are not certified nor recommended. When installing on Windows 7 ALWAYS choose a folder outside Program Files to avoid read-only file permission problems. We recommend a folder such as C:\IntraVUE.
If you install on a Server based system, you MUST use the Add Programs function of Control Panel's Add/Remove Programs.
|Virtualization||Any hypervisor platform that supports the operating systems above and that has a fixed virtual machine ID not subseptible to high-availability changes is required.|
JRE 8 32-bit will be installed as part of IntraVUE™ Installation. In 64-bit windows computers, only the 32-bit version of the Java Runtime Environment (JRE) should be installed (i.e. under C:\Program Files(x86)\Java).
|Security||Firewall software, and Antivirus software be disabled/turned off during the installation. You can turn them back on when the installation completes, and have configured firewall rules, and on-demand scanning exclusions to allow IntraVUE to scan.|
(will be installed as part of IntraVUE™ Server Installation)
*The C:\MySQL folder must be excluded from being backed up or analyzed by virus checking programs. The programs will lock critical, large files and cause the mysql service to stop if it cannot access certain files for longer than a few seconds. Should this occur, restarting the msyql service always works, but there will be no IntraVUE data collected while mysql is stopped.
|Apache Tomcat||Ver 6 (will be installed as part of IntraVUE™ Server Installation)|
The IntraVUE Server must be able to PING all the devices in the scan range. Open a dos command prompt and type "ping x.x.x.x" replacing x.x.x.x with the ip address of a device in the scan range. If the ping command returns "Reply from ..." without timing out then the device passed this requirement.
If any device is in a different subnet, you should be able to PING them using the TRACERT dos command (e.g. c:\> tracert "192.168.0.1." or similar) which will yield the last hop router leading to the device. The IP address previous to the target device in the output results is the gateway address required as top parent in the next section.
Layer 2/3 switches store the mac addresses of connected devices in the scan ranges and must be configured to respond to SNMP from the IntraVUE host. This requires that an SNMP Read-Only Community be configured on these devices and may require additional permissions such as an entry in an Access Control List (if applicable).
IntraVUE will not be able to map the full topology if SNMP is not enabled and SNMP Read-Only Communities are not configured on all L2/L3 switches in the plant floor. Install IntraVUE and use the switchprobe utility to confirm this requirement before proceeding. See Verifying SNMP on Fully Managed Switches.
When enabling SNMP and SNMP Read-Only Communities on some L2/L3 switches you may be required to perform a reboot to allow changes to take effect.
The switches must provide timely responses to SNMP queries. Typical response times are less than 20 milliseconds but some switches are known to take 20 seconds (20000 millisends). IntraVUE will tolerate a response as slow as 1000 milliseconds (1 second).
Switch responses must conform to SNMP standards and managed switches must respond to the Bridge Mib, RFC 1493 or one of its successors.
|Scanning Requirements in detail|
|ICMP Support:||The host Server must be able to PING all the devices to be scanned|
|Local Access||The devices storing the MAC addresses of the devices must be in the scan range|
|SNMP read only community||Minimum requirement for switches and routers|
|Access Control Lists:||May need configuration to allow access to SNMP data|
|Firewalls:||These can stop traffic between the IntraVUE Server and the networks to be scanned|
|HTTP Access||Necessary for access to the IntraVUE client inside and outside the plant network|
|Network Connectivity:||The switches must provide timely responses to SNMP queries. Typical response times are less than 20 milliseconds but some switches are known to take 20 seconds (20000 milliseconds). IntraVUE will tolerate a response as slow as 1000 milliseconds (1 second).|
|SNMP Support:||Device responses must conform to SNMP standards and must be configured to respond to SNMP messages from the IntraVUE Server.|
Managed (Required). Must be able to respond to the Bridge MIB, RFC 1493 or one of its successors.
Ports used by IntraVUE
80 – used to find devices with web pages and to provide a link to those pages automatically. May also be used as additional port to browse to IntraVUE if it does not conflict with IIS.
8765 – mandatory port to browse IntraVUE
161 – used for SNMP
162 – used to listen for SNMP trap messages
137 – used to find NetBIOS names
44818 – used for Ethernet/IP CIP protocol
65402 – used for communication to IntraVUE Agents
65403 – used for communication to IntraVUE Agents
Open topic with navigation