I.3 Network traffic volumes
The following describes traffic volumes generated at communication based on the Central Console and Central Scope. Traffic arising from other types of communication is minimal and is not covered in this explanation.
- Organization of this subsection
(1) Amount of data generated during communication based on the Central Console
The following describes the amounts of data generated during communication based on the Central Console.
(a) Estimated traffic volumes between JP1/IM - View and JP1/IM - Manager (Central Console)
|
Activity |
Estimated data transferred (bytes) |
|---|---|
|
Display events in the Event Console window. |
((5,000 + {average data size per event}#1 × 1.5) × (number of events acquired when window refreshed)#2 + 2,500) × ({number of events generated since window was last refreshed}#3 / {number of events acquired when window refreshed}#2) |
|
Open the Event Search Conditions window, or click the OK button in the Event Search Conditions window. |
|
|
Perform an event search. |
((5,000 + {average data size per event}#1 × 1.5) × (number of events acquired when window refreshed)#2 + 2,500) × ({number of retrieved events}#5 / {number of events acquired when window refreshed}#2) |
|
Open the Event Details window. |
20,000 + {total byte size of the attribute names defined in the definition file for the extended event attributes for the event in question} × 1.5 + {average data size per event}#1 × 1.5 + {length of event-guide messages (max. 409,600)} |
|
Open the System Environment Settings window, or click the Apply button in the System Environment Settings window. |
|
|
Open the Settings for Event Receiver Filter window, or click the Apply button in the Settings for Event Receiver Filter window. |
|
|
Open the Severe Event Definitions window, or click the OK button in the Severe Event Definitions window. |
|
|
Click the OK button in the Settings for View Filter window, or click the OK button in the View List of Filters window. |
|
|
Apply the settings in the Preferences window. |
6,000 |
|
Open the Action Parameter Definitions window. |
1,750 + ({byte size of one action definition} + 140) × (number of action definitions) |
|
Click the Apply button in the Action Parameter Definitions window. |
3,200 + (({byte size of one action definition} + 140) × (number of action definitions)) × 2 |
|
Open the Action Log window. |
2,400 + ({byte size of the action command} + {length of the messages displayed in the Action Log Details window}) |
|
Open the List of Action Results window. |
1,850 + (500 + {byte size of the action command} + {length of the messages displayed in the Action Log Details window}) × (number of displayed actions) |
|
Click the OK button in the Conditions for Updating List of Action Results window, or close the List of Action Results window. |
1,600 |
- #1: Example of calculating the average data size per event
-
To find the average data size per event:
1. Using the jevexport command, output all the events generated during a set period of time to a CSV file. For details on the jevexport command, see the JP1/Base User's Guide.
2. Find the total number of bytes in the output CSV file.
3. Divide the total byte count by the number of generated events.
If events that generate data greater than the average size are output in close succession, the above estimation might be exceeded.
#2: This is the value set in Num. of events to acquire at update in the Preferences window. The default is 20 events.
#3: Find the number of events issued since window was last refreshed using the equation given below.
#4: A condition group is a pass condition group or exclusion-condition group.
#5: This is the value set in Num. of events to acquire in 1 search in the Preferences window. The default is 20 events.
- Equation for {number of events generated since window was last refreshed}
-
-
When Apply is set for Automatic refresh in the Preferences window:
Number of events generated since window was last refreshed =
{value set in Interval (default 5 sec.)}
× {number of events generated per second}
-
When Do not apply is set for Automatic refresh in the Preferences window:
Number of events generated since window was last refreshed =
{interval at which user refreshes Event Console (sec.)}
× {number of events generated per second}
-
(b) Estimated traffic volumes between JP1/IM - View and JP1/Base (manager)
|
Activity |
Estimated data transferred (bytes) |
|---|---|
|
Execute a command from the Execute Command window. |
(928 + {command length}) × (4# + {number of lines in the execution result}) |
#: The number increases if a warning message (KAVB2xxx-W) is output about the command execution, but this is an exceptional case and is not counted in the estimate.
(c) Estimated traffic volumes between JP1/IM - Manager (Central Console) and JP1/Base
|
Activity |
Estimated data transferred (bytes) |
|---|---|
|
Execute a command in an automated action (data relayed between JP1/IM - Manager (Central Console) and JP1/Base on the same host). |
(5,024 × 4#1)#2 |
|
Click Event Search Conditions on the Search Events page to search for events (data relayed between JP1/IM - Manager (Central Console) and JP1/Base on the target host). |
140#3 + (600#4 × {number of JP1 events matching the search conditions}) |
#1: The number increases if a warning message (KAVB2xxx-W) is output about the command execution, but this is an exceptional case and is not counted in the estimate.
#2: Maximum amount of data for one automated action request issued to JP1/Base 08-00 or later.
#3: Amount of data when the name of the destination event server is 16 bytes and the event ID is the only search condition.
#4: Data size of the JP1 event issued when a character string of about 100 bytes is trapped by the log file trapping function.
(d) Estimated traffic volumes between JP1/Base and JP1/Base
|
Activity |
Estimated data transferred (bytes) |
|---|---|
|
Execute a command from the Execute Command window or execute a command in an automated action (data relayed among JP1/Base that received the request, JP1/Base on the relay host, and JP1/Base on the target host). |
5,540#1 + (1,700 × (3#2 + {number of lines in the execution result}))#3 |
#1: Maximum amount of data for a command execution request.
#2: The number increases if a warning message (KAVB2xxx-W) is output about the command execution, but this is an exceptional case and is not counted in the estimate.
#3: Maximum amount of data in the command execution result. You can adjust the amount of data using the jcocmddef command. For details on this command, see the chapter on commands in the JP1/Base User's Guide.
(2) Central Scope traffic
The following describes the amounts of data generated during communication based on the Central Scope.
(a) Estimated traffic volumes between JP1/IM - View and JP1/IM - Manager (Central Scope)
|
Activity |
Estimated data transferred (bytes) |
|---|---|
|
Update of the data being monitored in the Visual Monitoring window since the last poll (where polling takes place at 5-second intervals). |
500 + (number of nodes) × 40 |
|
Change in the status or monitoring status of nodes being monitored in the Monitoring Tree window since the last poll (where polling takes place at 5-second intervals). |
64 + (number of nodes whose status or monitoring status has changed since the last poll) × 20 |
|
During monitoring from the Monitoring Tree window of JP1/IM - Manager (Central Scope), updating of tree configuration information since the last poll (where polling takes place at 5-second intervals). |
Sum of the data amount for each monitoring object#1 + sum of the data amount for each monitoring group#2 + sum of the data amount for each common condition#3 |
|
Display the Guide window by choosing View and then Guide in the Monitoring Tree window, or by choosing Guide from the pop-up menu in the Visual Monitoring window. |
1,400 + size of the guide-message |
|
Search for status change events by choosing View and then Search Status-Change Events in the Monitoring Tree window. |
90 × number of status change events for the selected monitoring node |
|
Add or change a common condition in the Common Condition Detailed Settings window. Note that no communication is entailed when the Common Condition Detailed Settings window is opened from the Monitoring Tree (Editing) window. |
100 + data amount for the common condition#3 |
|
Apply tree configuration information to JP1/IM - Manager (Central Scope) by choosing File and then Update Server Tree in the Monitoring Tree (Editing) window. |
100 + sum of the data amount for each monitoring object#1 + sum of the data amount for each monitoring group#2 + sum of the data amount for each common condition#3 |
|
Acquire all common conditions from JP1/IM - Manager (Central Scope) by choosing Options and then Acquire Latest Definition in the Monitoring Tree (Editing) window. |
100 + sum of the data amount for each common condition#3 |
|
Apply visual monitoring data to JP1/IM - Manager (Central Scope) by clicking the Update the Visual Monitoring Data of Server button in the Visual Monitoring (Editing) window. |
500 + (number of nodes) × 40 |
- #1: Data amount for each monitoring object =
-
200 + {length of monitoring node name} + {length of icon file name (when sent)}
+ {length of icon file name (when expanded)} + {length of background image file name}
+ {sum of attribute name lengths} + {sum of attribute value lengths}
+ {sum of individual condition attribute name lengths}
+ {sum of individual condition attribute name values}
+ {sum of lengths of status change condition names in monitoring group}
- #2: Data amount for each monitoring group =
-
200 + {length of monitoring node name} + {length of icon file name (when sent)}
+ {length of icon file name (when expanded)} + {length of background image file name}
+ {sum of attribute name lengths} + {sum of attribute value lengths}
+ {sum of lengths of status change condition names in monitoring group}
+ {number of status change conditions in monitoring group} × 40
- #3: Data amount for each common condition =
-
250 + {length of common condition name} + 10 × {number of specified event levels}
+ {sum of lengths of source event server names} + {length of object type}
+ {sum of lengths of object names} + {length of root object name}
+ {length of occurrence name} + {sum of user name lengths} + {message length}
+ {product name length} + {event ID} × 10
+ {sum of lengths of extended attribute names}
+ {sum of lengths of extended attribute values}
(b) Estimated traffic volumes between JP1/IM - Manager (Central Scope) and JP1/Base on a managed host
|
Activity |
Estimated data transferred (bytes) |
|---|---|
|
Select the Generate, Show Differences, or Add button in the Auto-generation - Select Configuration window. |
For work-oriented or server-oriented trees: JP1/AJS data amounts# + JP1/PFM data amounts# + Data amounts of JP1/Cm2/SSO version 8 or earlier# + Cosminexus data amounts# |
#: Estimate these data amounts using the tables below.
-
Estimating JP1/AJS data amounts
Table I‒7: JP1/AJS data amounts Equation
Item
Estimated data transferred for each item (bytes)
200
+ sum of a
+ sum of b
+ sum of c
+ sum of d
a:
Scheduler service
10
+ length of the scheduler service name
+ length of the character code
b:
Job group
20
+ length of the scheduler service name
+ length of the full name of the unit
+ length of the job group name
+ length of the comment name
c:
Root jobnet
20
+ length of the scheduler service name
+ length of the full name of the unit
+ length of the jobnet name
+ length of the comment name
d:
Execution agent
10
+ length of the scheduler service name
+ length of the root jobnet path
+ length of the job execution agent name
-
Estimating JP1/PFM data amounts
Table I‒8: JP1/PFM data amounts Equation
Item
Estimated data transferred for each item (bytes)
200
+ sum of e
e:
Service
310
+ length of host name
+ length of instance name
-
Estimating data amounts of JP1/Cm2/SSO version 8 or earlier
Table I‒9: JP1/Cm2/SSO data amounts Equation
Item
Estimated data transferred for each item (bytes)
400
+ sum of f
+ sum of g
f:
Server that performs monitoring with threshold value
50
+ length of host name
g:
Application to be monitored
20
+ length of host name
+ length of application name
-
Estimating Cosminexus data amounts
Table I‒10: Cosminexus data amounts Equation
Item
Estimated data transferred for each item (bytes)
200
+ sum of h
+ sum of i
+ sum of j
+ sum of k
+ sum of l
+ sum of m
+ sum of n
+ sum of o
+ sum of p
+ sum of q
+ sum of r
+ sum of s
+ sum of t
+ sum of u
+ sum of v
h:
Operations management domain
10
+ length of operations management domain name
+ length of operations management domain display name
i:
Host
10
+ length of operations management domain name
+ length of the name or IP address of the operations management agent machine
+ length of host display name
j:
Logical J2EE server
320
+ length of operations management domain name
+ length of logical server name × 7
+ length of host name
+ length of logical server display name
+ length of logical server name of the logical naming service being used
+ length of logical server name of the logical OTS being used
+ length of logical server name of the logical CTM being used
+ length of logical server name of the logical TCS being used
+ length of logical server name of the logical performance tracer being used
+ length of logical server name of the logical SFO being used
k:
Logical naming service
70
+ length of operations management domain name
+ length of logical server name
+ length of host name
+ length of logical server display name
+ length of logical server name of the logical smart agent being used
l:
Logical smart agent
20
+ length of operations management domain name
+ length of logical server name
+ length of host name
+ length of logical server display name
m:
Logical OTS
70
+ length of operations management domain name
+ length of logical server name
+ length of host name
+ length of logical server display name
+ length of logical server name of the logical smart agent being used
n:
Logical TCS
70
+ length of operations management domain name
+ length of logical server name
+ length of host name
+ length of logical server display name
+ length of logical server name of the logical TCS being used
o:
Logical CTM domain manager
120
+ length of operations management domain name
+ length of logical server name
+ length of host name
+ length of logical server display name
+ length of logical server name of the logical smart agent being used
+ length of logical server name of the logical performance tracer being used
p:
Logical CTM
70
+ length of operations management domain name
+ length of logical server name
+ length of host name
+ length of logical server display name
+ length of logical server name of the logical CTM domain manager being used
q:
Logical performance tracer
20
+ length of operations management domain name
+ length of logical server name
+ length of host name
+ length of logical server display name
r:
Logical SFO
70
+ length of operations management domain name
+ length of logical server name
+ length of host name
+ length of logical server display name
+ length of logical server name of the logical performance tracer being used
s:
Logical Web server
70
+ length of operations management domain name
+ length of logical server name × 2
+ length of host name
+ length of logical server display name
+ length of logical server name of the logical performance tracer being used
t:
J2EE application
20
+ length of operations management domain name
+ length of display name of J2EE application properties
u:
Imported J2EE application
50
+ length of display name of J2EE application properties
+ length of logical server name of imported logical J2EE server
v:
J2EE server mapping definition
50
+ length of logical server name of the logical Web server
+ length of logical server name of mapped logical J2EE server