Port Specifications for Cavisson Products

This section provides a brief architecture diagram, Inbound and Outbound connections from the machines and port specifications, and the information collected/stored via these connections.

Architecture Diagram

Below is the high level architecture diagram explaining the connections made by NS, ND, NO boxes. This diagram also illustrates the ports used for these connections within the application test/production monitoring environment.

There are pre-configured ports to perform specific tasks for all Cavisson products.

1

Firewall Details

Below table represents the inbound and outbound connection details from one machine to another along with the port number.

Protocol Source Destination Port Purpose
NetStorm (NS)/NDE
TCP Laptop/VPN Clients NS Machine 7890 Proxy Based Recorder
TCP Laptop/VPN Clients NS Machine 22 SSH login
TCP Laptop/VPN Clients NS Machine 80,443 For NS GUI – Controller1
TCP Laptop/VPN Clients NS Machine IPMI IP 22 SSH port
TCP Laptop/VPN Clients NS Machine IPMI IP 80,443 Web port
TCP Laptop/VPN Clients NS Machine IPMI IP 5900 KVM server port
TCP/UDP Laptop/VPN Clients NS Machine IPMI IP 623 Virtual Media
TCP Laptop/VPN Clients NS Machine 8001, 4431 For NS GUI – Controller2 (Optional)
TCP NS Machine NO 22 SSH
TCP NS Machine NO 7890 Proxy Based Recorder
TCP NS Machine NO 7891 Cavisson Monitoring System
TCP NS Machine NO 80, 443 For HTTP/HTTPS Traffic
TCP NS Machine All SUT Servers 7891 Cavisson Agent
TCP ND Machine All SUT with JVM Controllers 7891 Cavisson NetDiagnostics Collector (NDC)
TCP NS Machine All Servers Under test (SUT) 22 SSH login (Optional)
TCP NS Machine All Servers/VIP which are to be hit 80, 443 For HTTP/HTTPS Traffic
NetOcean (NO)
TCP NO Machine NS Machine 22 SSH login
TCP Laptop/VPN Clients NS Machine IPMI IP 22 SSH port
TCP Laptop/VPN Clients NS Machine IPMI IP 80, 443 Web port/Web SSL Port
TCP Laptop/VPN Clients NS Machine IPMI IP 5900 KVM server port
TCP/UDP Laptop/VPN Clients NS Machine IPMI IP 623 Virtual Media
TCP Laptop/VPN Clients NO Machine 7890 Proxy Based Recorder
TCP Laptop/VPN Clients NO Machine 22 SSH login
TCP Laptop/VPN Clients NO Machine 8001,4431 NO GUI for instance 1
TCP Laptop/VPN Clients NO Machine 80,443 NO HTTP/HTTPS Port for Controller 1
TCP SUT AppServers NO Machine 80,443 Virtualization and recording of backend HTTP/HTTPS services
TCP NO Machine Backend Servers 80,443 Recording of backend HTTP/HTTPS services
NetVision (NV) – Two IP Addresses are required in addition to IPMI
TCP Laptop/VPN Clients NV Machine IPMI IP 22 SSH port
TCP Laptop/VPN Clients NV Machine IPMI IP 80, 443 Web port, Web SSL port
TCP Laptop/VPN Clients NV Machine IPMI IP 5900 KVM server port
TCP/UDP Laptop/VPN Clients NS Machine IPMI IP 623 Virtual Media
TCP Laptop/VPN Clients NV Machine UI IP 80,443 NV UI
TCP Laptop/VPN Clients NV Machine UI IP 22 SSH login
TCP Internet NV Machine Data IP 80,443 NV Data
TCP Laptop/VPN Clients NV Machine UI IP 8001,4431 NV GUI for Controller 1 (Optional)
All Products (Optional)
TCP NS/ND/NO/NV Machine Email Server 25,587 For sending email using SMTP. Email server is the IP address of email server used by customer.
TCP NS/ND/NO/NV Machine FTP Server 21 For FTP
TCP NS/ND/NO/NV Machine NTP Servers 123 Port used for checking and synchronizing time with some other server (Time Server)
TCP NS/ND/NO/NV Machine Internet 80, 443 For hitting production, downloading build from http site
TCP NS/ND/NO/NV Machine * 22 For scp build from secure server using scp

*We will assign two IP addresses in NS, NDE, NV and NO. For now, use only one IP.

*Additional IP is needed for IPMI on each appliance (IPMI IP)

Data Captured via Connections

Primarily all monitoring data is collected / stored over these connections. This data comes from monitors, agents deployed on applications and servers. This monitoring data is in the form of System metrics and Application metrics.

Data Captured by CMON (For NS and ND Only)

There are lots of application-specific monitors for applications, such as, JBoss, WebSphere, Java GC, Coherence, Hadoop, database, SNMP, logs etc. CMON also provides metrics of system level monitoring, such as disk stats, CPU, Memory, I/O etc. These monitors help in collecting performance-related information via connections made by agents.

For example:

ND receives following monitoring data from CMON monitor on port 7891 on the performance of WebLogic servers:

  • Weblogic JDBC Pool Stats
  • Weblogic JMS Queue Stats
  • Weblogic JVM Stats
  • Weblogic Thread Pool Data
  • Weblogic Min Thread Constraint Data
  • Weblogic Servers Health Stats
  • Weblogic Sessions Stats
  • Weblogic Transaction Name Data

Data Captured by BCI Agent (For ND Only)

  •     Http and Non Http transactions
  •     Response time, TPS, Errors, Methods calls, Back end calls, CPU time and other KPIs
  •     Http headers, cookies, status code etc.
  •     Package, class, methods etc.
  •     External calls like database, Http, web services etc.
  •     Exceptions (Handled and Un handled), errors, stack trace etc.
  •     Database queries
  •     Heap dump and Thread dump, stack trace etc.
  •     Thread callouts
  •     Logs messages

Data Captured by Node JS Agent (For NS and ND Only)

  • Http transactions
  • Response time, TPS, Methods calls, Back end calls and other KPIs
  • Package, modules, functions etc.
  • External calls like database, Http etc.
  • Database queries
  • Heap dump and CPU profiling, stack trace etc.