OMEGAMON XE for Mainframe Networks v5.3 Long presentation

© 2015 IBM Corporation
OMEGAMON XE for Mainframe Networks v5.3
Long presentation
September 2015

© 2015 IBM Corporation2
OMEGAMON Performance Management Suite
Improved visibility and management for z/OS and subsystems
zOS DB2 CICS IMS MQ NetworksStorage WAS
Provides complete management capability to improve Service Levels, increase
efficiency of resources and personnel while lowering overall costs.
New to Version 5.3.1 provides the following:
 Increased efficiency - Enhanced 3270ui Near Term Historical capability introduced to provide
combined real-time and historical problem analysis from the same user interface
 Decreased problem resolution time and effort for complex multi-domain problems through
integration on a single workspace (z/OS, CICS, Messaging, Storage, etc.).
 Reduced total Time to Value (TTV) - First time user PARMGEN function can help users see
OMEGAMON value in just a couple of hours.
 Reduced total Cost of Ownership (TCO) - Improvement in customer experience with a 35%
decrease in time of installation, configuration and maintenance across the whole OM family
DE
New Release New Release New Release New Functions
OMEGAMON Performance Management Suite V5.3.1

OMEGAMON Performance Management Suite V5.3.1
Version 5.3.1 provides the following (Continued):
 Decreased TCO - Continuing architecture modernization, code re-work, and leveraging
offload (zIIP) where appropriate to reduce resource usage and address spaces
 Adopting the V5.3.1 suite now provides leveraging of introduced value (reducing address
spaces, CPU savings, increased productivity) there is no benefit by waiting
 Maximize efficiency and reduce cost - Continues to provide best of breed alerting capabilities
allowing for ability to manage by exception and automation
 Improved support for new Technologies, support new platform/subsystem, mobile and cloud,
by enhanced performance management and integration across monitoring and automation.
 Includes individual product enhancements and capabilities such as day one support, Near-
Term history, integration, new metrics in the Enhanced 3270UI
Jim
Subject Matter Expert
Annette
Operations Analyst
Zach
Senior SysProg
Doug
IT Operations Manager
Working together
for an integrated
capability and
common goal:
Efficiency,
Effectiveness &
Collaboration

OMEGAMON XE for Mainframe Networks V5.3

• Increased efficiency – enhanced 3270 user interface near-term
history capability introduced to provide real-time and historical
problem analysis from the same user interface
• Decreased problem resolution time and effort for complex multi-
domain problems through integration on a single workspace in the
enhanced 3270 user interface. Embedded data with z/OS and
messaging for improved applications monitoring.
• Reduced Time to Value (TTV) – first time user PARMGEN function
can help users see OMEGAMON value in just a couple of hours
• Reduced Total Cost of Ownership (TCO) – Improved customer
experience with a 35% decrease in time of installation, configuration
and maintenance across the whole OMEGAMON family
Jim
Subject Matter Expert
Annette
Operations Analyst
Zach
Senior SysProg
Doug
IT Operations Manager
Working together
for an integrated
capability and
common goal:
Efficiency,
Effectiveness &
Collaboration

 Understand information related to when the problem began with near-term history in the
enhanced 3270 user interface
Increased efficiency
Effortlessly explore data around
when the out of order segments
occurred
Easily see when an
application has high
percent out of order
segments and select
for details

Decreased problem resolution time and effort
 View TCP connections and z/OS
address space details together to
understand when network
performance is impacted by z/OS
resource constraints
 Zoom into OMEGAMON on z/OS
workspaces to investigate further
into bottlenecks, storage usage,
and WLM service classes

 View TCP connections and TCP
listeners for a queue manager’s
channel initiator address space to
understand if network
performance is impacting the
processing of messages.
 Navigate to OMEGAMON XE for
Mainframe Networks workspaces
to investigate further into any
potential network performance
issues

 Quickly FIND network
resources
or
 Locate TCP connections,
FTP sessions, FTP
transfers or TN3270
Sessions in your
enterprise
 Then navigate in context
or issue Take Action
commands against a
selected network resource

 Debug network problems faster
 Issue PING, NSLOOKUP and
TRACERTE commands while
viewing any workspace in the
enhanced 3270 user interface
 The command is issued from the
selected system and the output is
displayed in the Command and
Response Log workspace

 Investigate interfaces and OSA issues with
the OSA command
 Investigate issues with TCP/IP resources
with the TCPIP or TCPIPMENU commands
 Investigate issues with VTAM resources
with the VTAM or VTAMMENU commands
Improved navigation:
 Enterprise Network Workspaces menu
– Access using the E action or the
NETWORK or NETMENU commands

Customize filters and queries by
setting site or user profile variables
 When you navigate to a
workspace or invoke a command,
there are default values for query
and workspace filters
 Set site or user profile variables in
rtename.UKOBDATF dataset to
override the defaults

 View UDP endpoints data in
context of an Enterprise Extender
connection
 The UDP endpoints data displays
the byte rates, datagrams
discarded, and queued bytes for
all the EE connections on this
LPAR
 View additional information by
selecting one of the UDP
endpoints and navigating to the
UDP Connection Details
workspace

 Identify overall TCP/IP and VTAM
address space issues
– Discards or retransmits
– CPU percent
– Paging rate
– CSA and private storage
usage
 Navigate to VTAM Buffer Pools
summary and details workspaces

Identify gaps in monitoring and
issues with your monitoring agents
with the Enterprise Mainframe
Networks Health workspace
 Invoke HEALTH command from
any OMEGAMON XE for
Mainframe Networks workspace
 Verify monitoring agents are
online
 Verify that data collection is active
and configured correctly
 SNA Collector and TCP Collector
tabs provide additional information

Monitor your OSA-Express5S
adapters in the enhanced 3270
user interface
 Enterprise OSA-Express Ports
Overview
 OSA-Express Ports for Channel
 OSA-Express Ports for Interface
 OSA-Express5S Ports Details

z/OS Networking & Network
Management

z/OS Communications Server
“How z/OS communicates with the outside world”
z/OS Communications Server
Design
ed by
the
"Chief"
Lynn
Long
Designed by
the magnificent
Overbymeister
Network Attachment Drivers
z/OS
Network Layer Protocol Stacks
TCP/IP V4 TCP/IP V6 SNA
Network
Applications and
Services
FTP, TN3270 SMTP,
Pagent, SNMP, …
Network Communications APIs
TCP/IP and SNA
z/OS Differentiation and Value Add
Network
Adapters
Data
Serving
Web
Services
ApplicationsTransactions
CICS, IMS, DB2, MQ, WAS, WebSphere middleware,
IM software, Batch, Rational, Tivoli, ISV, RYO
IPv4
SNA
IPv6
Security High
Availability
Performance
NetworkManagementInterfaces
NetworkMgtProducts:Tivoli(Netview,
Omegamon,zSecure,TSOM),ISVs
z/OS Comm Server
Configuration Assistant
• Web Based GUI
• Part of z/OS Management
Facility
 Enables all key z/OS workload to
communicate with the outside world
 Every request for service and
response flows through Comm
Server
 Provides standard suite of TCP/IP
applications but with close
integration into z/OS
 Enables network connectivity using
standards based network protocols
 IPv4: Current internet protocol,
support for latest standards
 IPv6: Emerging next generation
Internet protocol
 SNA: Maintain existing customer
application investment
 Enable IBM and
ISV network
management
products to
provide
differentiated
value on System z
 Enable network
connectivity with
differentiated z/OS
Qualities of
Service
 Performance
 Security
 High
Availability

Why on z/OS?
In spite of perception that z/OS
networking doesn’t break, SLA’s
are at risk:
 Application changes
 Hybrid networks
 BYOD
 Device failures
 Network congestion
Why the network?
A well-managed network will allow
you to get on with running your
company.
 Prevent problems
 Work efficiently
 Maintain security
Why manage the network on z/OS?
Network systems programmer:
“A critical application is ‘broken’. We all get on a bridge call. Everyone says ‘My stuff is
okay. It must be the network.’ I need to be able to say it is not the network or at least not
my part of the network.”

Problem isolation
Application
Hardware or
network
z/OS
Comm
Server
Application:
• Applications
• TCP Listeners
• TCP Connections
• UDP Endpoints
z/OS Comm Server:
• TCP/IP
• IP layer
• TCP layer
• UDP layer
• Interfaces
• Address space
• VTAM
• Buffer pools
• EE
• HPR
• CSM
• Address space
• OSA ports
• OSA channel
• HyperSockets
• Interfaces
• Data center network
• Intranet
• Internet
Hardware or network:

Solve your z/OS networking problems

Networking problem indicators
22
Locating Problems
Hangs
Response Time
Failures
Retransmissions
Out of order
Duplicate ACKs
Window resets
Backlog rejections
Microcode
Utilization

z/OS Communications Server Monitoring Overview
Traces
z/OS
Communications Server
Resource Awareness
Metrics & Error Counts
OSA-Express
Buffers
Applications
TCP Connections
IPSEC
TN3270
EE/HPR
NMI API
OMEGAMON XE for
Mainframe Networks
SMF
Tivoli
Enterprise
Portal
Enhanced
3270 user
interface
Situations
Retries, Timeouts
Rejections, Utilization . . .

OMEGAMON History Overview
Tivoli Enterprise
Portal
• Short term (last 24
hours) from PDS
• Long term (> 24
hours) from TDW
Agent
TDW
z/OS
Comm
Server
PDS
ITM
Servers
Tivoli Common
Reporting
z/OS
Tivoli Data Warehouse
Persistent
Data Store
Enhanced 3270
user interface
• Near-term history
from PDS (all
data available)

At a glance, view
key information for
each OMEGAMON
product
Navigate quickly through
the data to identify the
source of a problem
 Understand transactions across your enterprise
 Color coding to provide ability to find and resolve problems quickly
 Eliminates need to move between multiple screens and monitors
“GUI on a green screen”
Enhanced 3270 user interface creates Enterprise
wide view of information for improved availability

 Customized screens focused on customer defined problems
 Screen content based on high priority problems
 Includes Healthcheck and Bottleneck analysis
Gain graphical
view of data
Top consumers
view of details
Easy to see and find critical system and sub-system information for
improved performance and availability across System z
Customer prioritized Problem Solving scenarios
built into enhanced 3270 user interface

“As a network SME, I need to navigate quickly through the data, identify the source of a
problem, and resolve the problem through take action commands…”
Choice of user interfaces:
Enterprise wide workspaces and searches to quickly
identify, at a glance, poorly performing resources
Enterprise_Networks navigator
in the Tivoli Enterprise Portal
Enterprise Network Workspaces
in the enhanced 3270 user interface

Finding a Connection - FAST
28
Dynamic Query
Connections
TN3270
FTP Sessions
FTP Transfers
Wild Card '*'
IP Addresses
Ports
Applications
Connection States
TN3270 LOGMODEs
TELNET Names
FTP DSN
USERIDs
Enterprise FINDS FIND By - Examples:
Diagnose
Enterprise Connections FIND

IP Security (IPSec)
Overview
 Network layer Security
 Driven by filters
 Difficult to debug
 IP Filter Statistics
 HPR Maps to UDP
 Tunnel Details
 High Retransmissions
 Out of Sequence
Results
– Diagnose IPSEC tunnels and IP
filters
– Unique to OMEGAMON

Synergy with IBM Tivoli NetView for z/OS
 Launch in context to start or
stop a NetView packet trace
1. Select TCP connection to trace
2. Logon to NetView
3. View packet trace definitions
after link script completed
2
1
3

Sample situations trigger NetView for z/OS automation
 Execute command in NetView address space
 Send situation information in message
Sample NetView for z/OS
automation
 Recognize messages
 Recognize situation events
 Parse message text
 Parse Situation event
Synergy with IBM Tivoli NetView for z/OS

Integration with IBM Operations Analytics
OMEGAMON + IBM Operations Analytics – Launch in Context from TEP
The One Two – Punch: Combine two very powerful tools to ensure performance and
high availability of your enterprise.
• Perform log analysis in context of OMEGAMON workspaces – This approach
enables OMEGAMON users to perform in-context log analysis while doing problem
determination
• From your OMEGAMON workspace, use the IOA search bar to search logs (using LPAR or
Sysplex as the default context)
• Easy to implement - Configure TEP to display the IOA search bar
32
Launch IOA from
OMEGAMON performance
monitoring workspaces to
search logs in context

Network diagnostic commands
PING, NSLOOKUP, TRACERTE and DROP
TEP Scenario:
 Situation alert created when connection experiences slow
response time
 SME navigates to Connections workspace and sees high
retransmission rate for a connection
 Is there high congestion in the network?
 Right clicks on the row for connection and choose
Tracerte to display Tracerte dialog.
 Issues Tracerte to understand route between the two
hosts and if router that is not working
Enhanced 3270 Scenario:
 Situation alert created when connection
experiencing slow response time
 SME navigates to Application TCP Listeners and
Connections workspace and identifies connection
 SME types the “/” option to display a list of options
 Types “D” to display the Drop dialog
 Issues Drop and verifies connection dropped

Troubleshoot data collection problems
 Agent Status
workspace provides
configuration and
status information
about the agent and
its data collectors.
 Troubleshoot data
collection problems
resulting in missing or
incomplete data
– After an install or
upgrade
– After the agent has
been running for
some time
 New attributes display
status of data
collection interfaces

Increased System Availability with
faster problem resolution

OMEGAMON XE for Mainframe Networks delivers
problem solving scenarios for your network
Monitor your:
 Applications and TCP listeners
 OSA and interfaces
 TN3270 servers and sessions
 FTP sessions and transfers
 TCP/IP stacks
 Enterprise Extender connections and HPR pipes

Scenario:
Scheduled logons and “silent” failures
The setting:
A mainframe network systems programmer was building a baseline for network
performance of his LPARs and applications. A very high number of rejected connections
were being reported by OMEGAMON XE for Mainframe Networks just after 10 pm each
evening. At first, the systems programmer thought he had found a problem with the
monitoring software.

1. Johann, the network
systems programmer,
enabled a situation that
e-mails him when
backlog connections are
rejected.
2. The e-mails confirmed
that thousands of
connection requests
were being rejected
before the FTP server
was able to accept.

Scheduled logons and “silent” failures …
3
4
5

6

7

She then navigates to the Application
TCP Listeners and Connections
workspace to view the current
connections to the FTP server.
The backlog limit is 10, which is low.
She reconfigures the FTP server to
have a backlog limit of 50.
8
9

That evening starting at 10 pm,
the FTP server was accepting
connections as usual, but the
backlog limit is quickly exceeded
and subsequent connections are
rejected.
10 The OMEGAMON operator again verifies that the FTP application is accepting
connections, and the connections in backlog returns to zero by 10:30 pm. She
calls the network expert to update her on the problem.
When she investigates further, the network expert finds that 10,000+
workstations all “wake up” at the same time and attempt to FTP files at 10pm
every night.
She increases the backlog limit for the FTP sever temporarily to 2000 to provide
relief until desktop support can roll out a change to the automated nightly timer,
staggering the FTP connection requests over a couple of hours.
11
12

Scenario:
Spotting trends in abnormal connection count
The setting:
In this use case, a network systems programmer needs to identify the reasons behind
slow, steady growth in the number of connections in one IMS region.
The network systems programmer navigates to the Enterprise Applications Health
(KN3TAPO) workspace to view the IMS applications.

Spotting trends in an abnormal connection count …
1
2
3
The workspace
shows only IMS
regions.
He observes the
values of Connection
Count and Active
Connections High
Water Mark

4
IMSBYCON has a
higher connection
count than the other
IMS regions.
He contacts an IMS systems programmer who
verifies that all the IMS regions, including
IMSBYCON, are performaing work and no one has
reported any connectivity issues.
5
6 There are no connections in
backlog and the Idle Time
shows that the IMS region is
accepting connections
7

He observes the IMS regions over time, watching
the Connection Count increase while the Idle Time
and Connections in Backlog remain in a normal
range.
Friday:
Monday:
8
He again contacts the IMS systems programmer.
By now, 1000+ connections are open, but not
performing any work.
They determine that connections are being opened
that are not being closed. The recycle IMS server to
relieve the problem and the IMS programmer further
investigates the IMS region.
9

Scenario:
Why can’t users access an application?
The setting:
Saurabh, the network expert, is receiving reports of several
users having issues accessing an application. He has one
user’s IP address and plans to use it to research this issue.
He decides to try the new OMEGAMON for Mainframe
Networks Enterprise Connection Find workspace to debug
the problem.
.

Scenario:
Congested OSA Interface
The setting:
A systems programmer needs to quickly identify whether one OSA is processing a
significantly higher volume of traffic than the other OSA on LPAR SP12. Traffic should be
evenly distributed between the two OSA ports.

Congested OSA interface …
1

Congested OSA interface …
2
He issues a D TCPIP OMP RTTABLE command to
display the main OMPROUTE table and determines
that a first hop switch is congested for the non-
productive OSA.
He contacts the enterprise networking team to
resolve.
3

Scenario:
TN3270 connectivity problems
The setting:
A user has reported a problem accessing a 3270 application using a TN3270 session.
Since the enterprise has more than 10,000 TN3270 connections, systems programmers
cannot chase down individual connection issues.
However, after more users call with a similar complaint, a systems programmer starts to
investigate.

TN3270 connectivity problems …
He navigates to the Enterprise TN3270
Servers Overview workspace
1
2
He knows that this 3270 application is accessed
using a distributed DVIPA. He needs to look at the
TN3270 servers in the PLEX3 sysplex.
He presses F4 to bring up the Filter Detail menu,
specifies the Sysplex Name filter as “= PLEX3“
and returns to this workspace.

3
4

5
No active sessions have remote
IP addresses in the same subnet
as the users reporting the
problems.
6
He types an A in the action field to
navigate to the TN3270
Connections for Port
Port_Number workspace
7

To view only closed
sessions, he adds a filters
on Session Indicator with
a value of 2.
8

He determines that some closed sessions
have remote IP addresses in the reported
subnet, but all of those connections ended
more than an hour ago.
This is likely a router issue. He contacts
network support.
9

Scenario:
The setting:
A mainframe network systems programmer was building a baseline for network
performance of his LPARs and applications. A very high number of rejected connections
were being reported by OMEGAMON XE for Mainframe Networks just after 10 pm each
evening. At first, the systems programmer thought he had found a problem with the
monitoring software.

1. Johann, the network
systems programmer,
enabled a situation that
e-mails him when
backlog connections are
rejected.
2. The e-mails confirmed
that thousands of
connection requests
were being rejected
before the FTP server
was able to accept.

3
4
5

6

7

8

That evening starting at 10 pm,
the FTP server was accepting
connections as usual, but the
backlog limit is quickly exceeded
and subsequent connections are
rejected.
9 The OMEGAMON operator again verifies that the FTP application is accepting
connections, and the connections in backlog returns to zero by 10:30 pm. She
calls the network expert to update her on the problem.
When she investigates further, the network expert finds that 10,000+
workstations all “wake up” at the same time and attempt to FTP files at 10pm
every night.
She works with desktop support to roll out a change to the automated nightly
timer, staggering the FTP connection requests over a couple of hours.
10
12

Scenario:
Spotting trends in abnormal connection count
The setting:
In this use case, a network systems programmer needs to identify the reasons behind
slow, steady growth in the number of connections in one IMS region.
The network systems programmer navigates to the Enterprise Applications Health
(KN3TAPO) workspace to view the IMS applications.

1
2
3
The workspace
shows only IMS
regions.
He observes the
values of Connection
Count and Active
Connections High
Water Mark

4
IMSBYCON has a
higher connection
count than the other
IMS regions.
He contacts an IMS systems programmer who
verifies that all the IMS regions, including
IMSBYCON, are performaing work and no one has
reported any connectivity issues.
5
6 There are no connections in
backlog and the Idle Time
shows that the IMS region is
accepting connections
7

He observes the IMS regions over time, watching
the Connection Count increase while the Idle Time
and Connections in Backlog remain in a normal
range.
Friday:
Monday:
8
He again contacts the IMS systems programmer.
By now, 1000+ connections are open, but not
performing any work.
They determine that connections are being opened
that are not being closed. The recycle IMS server to
relieve the problem and the IMS programmer further
investigates the IMS region.
9

Scenario:
Determining stack health using throughput
The setting:
A network systems programmer needs to identify issues with the throughput of network
traffic through the z/OS TCP/IP stacks in the enterprise.
She is notified of slow network performance on one or more systems. These problems
do not appear to be associated with any particular application

Determining stack health using throughput …
2
1

3
He reviews the IP Layer
Metrics. There are no
datagrams discarded.
The TCP Layer Metrics subpanel
reveals that there have been segments
retransmitted and out of order segments
on LPAR SP13.
4

Scrolling to the right, he
notices that Total Out of
Order Segments is growing.
5
He types / and presses
Enter next to SP13 to
display the Options Menu.
He types I and presses
Enter to navigate to the
TCPIP Stack IP
Performance Details
workspace
6
7

There have been no fragmentations
8
9
He determines that a configuration error on
another system is causing the high number of
reassemblies in the IPv4 layer. He corrects the error
and confirms that the reassemblies stop.
10

Scenario:
What is slowing down my business partner’s
applications?
The setting:
Annette is an Operations Analyst.
Today, she received reports of slow response time with a
Business Partner’s application. She knows that the
Business Partner’s network is connected to her
company’s network through Enterprise Extender (EE)
Connections..

What is slowing down my business partner’s applications?

http://www.youtube.com/playlist?list=PLiD3_RDV00JcpfI2GCf2mPqprba2KZCsP
YouTube videos of problem solving scenarios:

THANK YOU!

 96
OM XE
MfN
CANSN3
OM II
MfN
CANSON
ETE
CANSETE
HUB
TEMS
TEPS
OMEGA
VIEW
OM XE
MfN
CANSN3
OM II
MfN
CANSON
ETE
CANSETE
LPAR 2
LPAR 1
KONACTCS
KONACTCS
KN3ACTCS
KN3TN3270
KN3FTP
KN3ACTCS
KN3TN3270
KN3FTP
OMEGAMON XE for Mainframe Networks
MfN Data Space
MfN Address Space
Common Addr Space
MfN Data Space
MfN Address Space
Common Addr Space
TOM
CANSTOM

Interface
Status
Interface
Statistics
DLC Read and Write
Queue Statistics
TCP Connections
OMEGAMON XE for Mainframe Networks provides:
Visibility into the zEnterprise IntraNode
Management Network (INMN) and
zEnterprise IntraEnsemble Data Network
(IEDN)
• Isolate and analyze traffic
flowing over zEnterprise
private networks
Visibility into z/OS applications
and connections using the new
zEnterprise Management
Network with performance metrics that are
useful in debugging problems
• Filter on Outbound Interface Name to
show connections using the new
INMN and IEDN interfaces
Support for zEnterprise mainframe server improves
application availability

OMEGAMON XE for Mainframe Networks v5.3 Long presentation

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to OMEGAMON XE for Mainframe Networks v5.3 Long presentation

Similar to OMEGAMON XE for Mainframe Networks v5.3 Long presentation (20)

More from IBM z Systems Software - IT Service Management

More from IBM z Systems Software - IT Service Management (20)

Recently uploaded

Recently uploaded (20)

OMEGAMON XE for Mainframe Networks v5.3 Long presentation