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.

ProtocolSourceDestinationPortPurpose
NetStorm (NS)/NDE
TCPLaptop/VPN ClientsNS Machine7890Proxy Based Recorder
TCPLaptop/VPN ClientsNS Machine22SSH login
TCPLaptop/VPN ClientsNS Machine80,443For NS GUI – Controller1
TCPLaptop/VPN ClientsNS Machine IPMI IP22SSH port
TCPLaptop/VPN ClientsNS Machine IPMI IP80,443Web port
TCPLaptop/VPN ClientsNS Machine IPMI IP5900KVM server port
TCP/UDPLaptop/VPN ClientsNS Machine IPMI IP623Virtual Media
TCPLaptop/VPN ClientsNS Machine8001, 4431For NS GUI – Controller2 (Optional)
TCPNS MachineNO22SSH
TCPNS MachineNO7890Proxy Based Recorder
TCPNS MachineNO7891Cavisson Monitoring System
TCPNS MachineNO80, 443For HTTP/HTTPS Traffic
TCPNS MachineAll SUT Servers7891Cavisson Agent
TCPND MachineAll SUT with JVM Controllers7891Cavisson NetDiagnostics Collector (NDC)
TCPNS MachineAll Servers Under test (SUT)22SSH login (Optional)
TCPNS MachineAll Servers/VIP which are to be hit80, 443For HTTP/HTTPS Traffic
NetOcean (NO)
TCPNO MachineNS Machine22SSH login
TCPLaptop/VPN ClientsNS Machine IPMI IP22SSH port
TCPLaptop/VPN ClientsNS Machine IPMI IP80, 443Web port/Web SSL Port
TCPLaptop/VPN ClientsNS Machine IPMI IP5900KVM server port
TCP/UDPLaptop/VPN ClientsNS Machine IPMI IP623Virtual Media
TCPLaptop/VPN ClientsNO Machine7890Proxy Based Recorder
TCPLaptop/VPN ClientsNO Machine22SSH login
TCPLaptop/VPN ClientsNO Machine8001,4431NO GUI for instance 1
TCPLaptop/VPN ClientsNO Machine80,443NO HTTP/HTTPS Port for Controller 1
TCPSUT AppServersNO Machine80,443Virtualization and recording of backend HTTP/HTTPS services
TCPNO MachineBackend Servers80,443Recording of backend HTTP/HTTPS services
NetVision (NV) – Two IP Addresses are required in addition to IPMI
TCPLaptop/VPN ClientsNV Machine IPMI IP22SSH port
TCPLaptop/VPN ClientsNV Machine IPMI IP80, 443Web port, Web SSL port
TCPLaptop/VPN ClientsNV Machine IPMI IP5900KVM server port
TCP/UDPLaptop/VPN ClientsNS Machine IPMI IP623Virtual Media
TCPLaptop/VPN ClientsNV Machine UI IP80,443NV UI
TCPLaptop/VPN ClientsNV Machine UI IP22SSH login
TCPInternetNV Machine Data IP80,443NV Data
TCPLaptop/VPN ClientsNV Machine UI IP8001,4431NV GUI for Controller 1 (Optional)
All Products (Optional)
TCPNS/ND/NO/NV MachineEmail Server25,587For sending email using SMTP. Email server is the IP address of email server used by customer.
TCPNS/ND/NO/NV MachineFTP Server21For FTP
TCPNS/ND/NO/NV MachineNTP Servers123Port used for checking and synchronizing time with some other server (Time Server)
TCPNS/ND/NO/NV MachineInternet80, 443For hitting production, downloading build from http site
TCPNS/ND/NO/NV Machine*22For 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.