Skip to main content

Deployment Requirements

This section explains the deployment requirements for the RN150 Virtual Appliance.

The RN150 is a Debian/GNU Linux Virtual Appliance. It is deployed on either VMware ESXi (6.5 or later) or Microsoft Hyper-V (Server 2019 or later).

Resource Requirements

The following are the default resource requirements.

RequirementDescription
RAM8 GB of RAM
vCPUs2 vCPUs
Hard drive space50 GB Hard drive (Thin Provisioned)
Internet access (TCP Port 443)TCP Port 443 outbound to the following: orchestration.riscnetworks.com (34.192.184.110, 34.192.195.90) initial.riscnetworks.com (34.192.43.78, 34.192.198.28) dataup.riscnetworks.com (34.192.12.37, 34.192.197.132) app1.riscnetworks.com (34.192.198.73) Backup & Growth (34.192.99.153, 34.192.185.36)
Internet access (UDP Port 123)UDP Port 123 outbound to the following: ntp.riscnetworks.com (3.231.5.12, 18.204.38.15, 52.70.0.210) If this requirement cannot be met, due to, for example, requiring a proxy, a local NTP server can be specified instead, or NTP can be disabled which will automatically enable hypervisor host timesync. See Appliance NTP Support for details.

Communication Protocols

The RN150 uses the following protocols (ports) to access the network. These protocols/ports should be permitted between the RN150 and all local resources (servers, routers, etc) to be included in the discovery.

ProtocolPortSourceDestinationUsage
TCP443RN150InternetFor communication from the RN150 to the RISC Networks Cloud Orchestration layer
TCP443RN150FlexDeployFor uploading inventory/performance data and synchronizing licensing This communication protocol is not applicable to SaaS engagements.
UDP123RN150InternetFor synchronizing appliance time via NTP
ICMPRN150Local NetworksBy the RN150 for base discovery for available devices
TCP135RN150Local NetworksBy the RN150 to obtain WMI information from Windows hosts discovered
TCP1025-5000RN150Local NetworksRPC Dynamic Port Allocation used for WMI communication (Default for Windows Server 2003 / XP and older)
TCP49152-65535RN150Local NetworksRPC Dynamic Port Allocation used for WMI communication (Default for Windows Server 2008 / Vista and newer)
TCP80RN150Local NetworksBy the RN150 to obtain HTTP
UDP161RN150Local NetworksUsed for gathering SNMP information from devices on the Network
TCP443RN150Local NetworksUsed for gathering VMware guest information directly from vCenter
TCP22RN150Local NetworksBy the RN150 to collect from Linux/UNIX servers over the SSH protocol
TCP*RN150Local NetworksCollection from Linux/UNIX servers via SSH user supplied non-standard TCP ports
TCP445RN150Local NetworksSMB over TCP/IP used for application socket collection
TCP139RN150Local NetworksSMB over NetBIOS used for application socket collection
TCP8443RN150Local NetworksUsed for discovering Tomcat and Cisco UC servers*
TCP62078RN150Local NetworksUsed for discovering Apple products (iPhone) – iTunes sync over air port
TCP22RN150Local NetworksFor command line discovery of Cisco Switches and Routers
TCP1433**RN150Local NetworksFor MSSQL database collection only
TCP1521**RN150Local NetworksFor Oracle database collection only
TCP3306**RN150Local NetworksFor MySQL database collection only
note

Double asterisks (**) means that port or other non-standard ports as required for database connectivity.

Required Credentials and Parameters

The following are required credentials and parameters:

Credential/ParameterDescription
IP SubnetsIP Subnets that the client would like to scan These can be added at the time the RN150 is deployed. Subnets can be manually entered or a routing table can be used to populate the list via SNMP
AdministratorsWindows Domain Administrator or Local Administrator (workgroup servers only) credentials Needed for WMI access
SSH User AccountSSH user account with sudo privileges Password or key-based authentication For more information, see SSH Collection Module.
SNMP Read-Only CredentialsNeeded for Linux/Unix Servers where not using SSH and should include the following MIBs: Host-Resources-MIB UCD-MIB IF-MIB TCP-MIB UCD-DISKIO-MIB Needed for Network Devices Supports v1/v2/v3
VMware CredentialsRead-only access to vCenter or root access to ESX hosts directly
Database credentialsIP/SIDs of database hosts For more information, see Database Module.