Need assistance monitoring network traffic of a JVM with a remote server
search cancel

Need assistance monitoring network traffic of a JVM with a remote server

book

Article ID: 222207

calendar_today

Updated On:

Products

NetMaster Network Automation NetMaster Network Management for TCP/IP

Issue/Introduction

How to monitor network traffic of a JVM with a remote server

Environment

Release : 12.2

Component : CA NetMaster Network Management for TCP/IP

Resolution

If you want to monitor traffic to '200.218.66.140.. port 16422 (external IP)'.

 

If that's the case, they could setup a /IPAPPLs definition like follows:

 

Application Name Entry                                                                
  Order...................... 100              (0 - 32766)                            
  Application Name Base ..... JVM                                                     
Connection Match Criteria                                                             
  Application Jobname .......                                                         
  TCP/IP Stack Jobname ......                                                         
  Local Port (low/only) .....                  (0 to 65535)                           
  Local Port (high) .........                  (0 to 65535)                           
Remote Address (low/only)   192.0.2.xxx                                          
Remote Address (high) ..... 192.0.2.xxx                                          
  Remote Port (low/only) .... 16422            (0 to 65535)                           
  Remote Port (high) ........ 16422            (0 to 65535)                           
Processing Options                                                                    
  Generate Name ............. ASIS             (Asis, LPort, Jobn, RAddr/RPort)       
  Deliver Records ........... NONE             (None, Init, Term, or Both)            
  Write INIT Records ........ DEFAULT          (Write, NoWrite, Default)              
  Write TERM Records ........ DEFAULT          (Write, NoWrite, Default)              
  Write zERT Records ........ DEFAULT          (Write, NoWrite, Default)              
  Collect Statistics? ....... YES              (Yes or No)                            
  Expiry Period ............. 0                (0 to 999 minutes)      


Then setup any alerting they want for the 'bytes transferred for application' attribute.   

That's if the JVM is creating a connection to that remote device and sending traffic.

Resource ......... TCPIP (STACK)                                             
Attribute ........ ConBytes                                                    
Description ...... Bytes transferred for application                           
Qualifier ........ JVM                                                    
Baseline Type ...+           (Daily, DayOfWeek or HourOfDay)                   
Three Strike Alert NO        (YES or NO)                                       
                             S/U=Update A=Actions C=Clear Actions R=Reset Alert
                                                  Max                          
    Alert Type          Summary                   Sev  Act#  Alert Description 
    High Rate Alert                                -      -                    
    Low Rate Alert                                 -      -                    
    Above Baseline Rate                            -      -                    
    Below Baseline Rate                            -      -                    

Additional Information

To verify it -

Given that there's a qualifier of JVM when doing the updates to the Workload Connection screen, that means JVM must be out there.  Please try the following to see what the stats are for that connection:

=/PERF

s    Business Views             Business Applications    

s    JVM       NNNN   14:00      468.7K      5.0         -   

h     ConBytes   

 

Is there traffic being shown?

They can do PF12 to toggle between DAYS, WEEKS, HOURS