Basic Netcool Understanding - Day 2: © 2006 IBM Corporation
Basic Netcool Understanding - Day 2: © 2006 IBM Corporation
Agenda
• Introduction
• Why we need netcool
• Netcool vs Other NMS tools
IBM Software Group | Lotus software
• Netcool suite of products High level Overview
(OMNIBUS, WebGUI, Impact, ITNM, TBSM)
IBM Software Group
Introduction
Traditionally, the IBM Netcool solution follows the CCAI methodology:
C -> Collection Layer This layer is the one which is in actual contact with the Network, it
pulls or would get pushed the Fault events or Topology information or Performance
info. Typically the Probes, the Agents (which do the auto-discovery) in Precision Family
and the DataLoad in Proviso belong to this layer.
C -> Consolidation Layer This layer aggregates the information collected by the Collection
Layer and stores them. It also gives tools to manage this information, be it Fault,
Topology orIBM Software
Performance. Group
ObjectServer, | Lotus
Precision software
IP/TN Server(ITNM) and Datamart in
Proviso belong to this layer.
A -> Analysis Layer This layer processes the information gathered in the Consolidation
layer. Examples are, Impact which can be used to enrich the ObjectServer data or the
RCA (Root Cause Analysis) engine in Precision IP.
I -> Inform Layer This is the colorful layer which informs the user about the collected,
consolidated and analyzed Fault/Topology/Performance information. The information
could be passed on as Charts, Maps or Reports. WebGUI, Topoviz (part of the Precision
family) and Dataview in Proviso.
IBM Software Group
Agenda
• Introduction
• Why we need netcool
• Netcool suite of products High level Overview
IBM Software Group | Lotus software
(OMNIBUS, WebGUI, Impact, ITNM, TBSM)
IBM Software Group
Agenda
• Introduction
• Why we need netcool
• Netcool suite of products High level Overview
IBM Software Group | Lotus software
(OMNIBUS, WebGUI, Impact, ITNM, TBSM)
IBM Software Group
• OMNIbus
• WebGUI
• Impact
• ITNM
• IBM Software Group | Lotus software
Proviso
• TBSM
• Reporter
IBM Software Group
Introduction
Netcool OMNIbus
Omnibus is the heart of Netcool Suite and is the core behind IBM Netcool Fault
Management solution.
Object Server is the repository for the Fault events collected from the network.
It is a memory resident database, which makes the event processing faster thus enabling
Netcool to provide robust, alarm storm tolerant Fault Management Solution.
Gateway:
is a piece of software that enables the Object Server to interface with other 3rd party
applications / Object server. Thus giving the Object Server the capability to talk to other
NMSes / EMSes.
IBM Software Group
Introduction
WebGUI
WebGUI Screenshots
WebGUI Screenshots
Introduction
Netcool Impact
User can use Impact to develop code called policy which can be used to enrich the
ObjectServer events. Impact can talk to an external database which could be
provisioning database or SLA database and derive additional information w.r.t the
alarm and populate it back into the ObjectServer event.
IBM Software Group | Lotus software
Further, we can use these policies to find the Impact on the Services riding in th
Network and help the user prioritize his activities.
IBM Software Group
Introduction
ITNM
ITNM, would classify it as a product that does both Fault Management and to some extent
Configuration Management.
It is the product primarily used to Auto Discover the network and collect the Asset
information of the network elements.
Note that Precision doesn't have the capability to do Provisioning (sending commands
down to the Network element to change the behavior of the Network Element).
The main functionalities are:
Discovery: IBM Software Group | Lotus software
It automatically discovers the Layer 2 & 3 Network Elements, Models the collected
information and creates the Topological view of the Network. This is a pure Configuration
Management functionality.
ITNM Architecutre
ITNM Screenshots
Introduction
TBSM
TBSM Screenshots
Introduction
Netcool Reporter
Purple
Red
Light
Orange
Green
Yellow–Blue
Critical
–––Clear
Indeterminate
Minor
Major
– Warning
alarm
event.
alarm
alarm - Service
-No
-Non-service
–Service
An
active
event
impacting
impacting
alarms.
that
impacting
has
alarm.
alarm.
been
alarms
resolved.
All
BeforeNetcool we alarm
get too events
far into are color
Netcool,
This usually occurs when a problem has been resolved or cleared
Examples:
coded
let’s andby
look
the
severity,
at
node
Node
CPU the
back
alarm
or
down alarmand
interface
to(CPU
(NMS
normal
is
>=
lost categorized
colors
still
(CPU
85%
60%
network
returning
busy)
<=
< 60%
84% and
connectivity
tobusy)
busy)
normal. by
meanings status.that will be
to device)
Node unreachable
Interface error alarm
returned
(NMS
(>
(3% 5%
tolost
-normal
5%
interface
route
interface
(<to3error
device)
error
error
rate)
rate)
rate)
displayed
The
Memory
Network
severity
returned
alarm (>=in
(10
unreachable to%
10%the
color
normal
available
(NMS Netcool
<= 20%
(>
lost
indicates
20%
memory)
available
route console.
available
memory)
the importance or
memory)
to network)
Link down
SNMP agent
alarm
up
down
(NMS
(interface
alarm
can(String;
lost
query
carrier
device)
nms or
canLMI)
not query device)
urgency of the event, and the status indicates
Node
Bufferup
failure
(connectivity
alarm (buffer
restored
failures
to device)
have occurred on device)
Buffer is back to normal (alarm automatically clears after 4 hour waiting period)
whether the event has been acknowledged.
IBM Software Group | Lotus software
IBM Software Group
Netcool Interface
1. Network Status
There are 9 fields in the information displayed once an object has been selected:
1. Event ID- a system generated unique identifier number
2. Remedy Ticket - The Remedy ticket number, once it is assigned (BellSouth ticketing system)
3. IBM Software Group | Lotus software
Node - The device name for the affected route or device
4. City – The city in which the device is located
5. ACK – Indicates whether the alarm has been acknowledged.
6. Summary – A brief summary of the alarm
7. First Occurrence – A Date/Time stamp of the alarm, indicating the time/date when the device first
went into alarm
8. Count – The number of times a device has alarmed since the initial alarm
9. Last Occurrence - Date/Time stamp of the last time the system indicated an alarm
IBM Software Group
2. Alarm Summary
Compare
If we compare
Each the orange
Region the redcolor
icon Athens
Rome icon to the alarm
corresponds alarm color
color
to the mostcodes,
codes, we’ll
and we’ll
serious see
see
that
alarmthat
thewithin
most
the most
serious
thatserious
alarm
GTA alarm
in that
Region. in that
GTAGTA
Region
Region
is a Critical
is a Major
alarm.
alarm.
Click any ofthe
Remember thealarm
GTA color
Region alarm icons to open a list
codes?
with the details for those alarm events in that GTA Region.
This is the list generated by clicking the Rome icon.
IBM Software Group
4. Agency Status
Similar toClick
the GTA
any of Region
the Agency
status,alarm
the Agency
icons to icons
openrepresent
a list the highest
status ofwith
alarmtheevents
detailswithin
for those
eachalarm
Agency,
events
regardless
in that Agency.
of GTA Region.
Since
With
DMVS DNR,This
DJJ, yellow
they
has have
and isCSB
the resulting
Indeterminate
icons,red
DOC
icons,
are&clear,
as
DTAE
DHR list
thewith
andgenerated
highest
both
green
DLAW
have
level
icons for
Minor
both
alarm. DLAW,
indicating
have
events with
Critical
as
no the
current
events
highest
alarms.
asalarm.
most
the highest serious events listed first.
alarm.
IBM Software Group
Netcool Summary
Netcool is a fault management tool.
It is important to remember that Netcool doesn’t measure performance; it
only indicates the presence or absence of traffic from network devices
and routes.
Similar to a ping command, as long as traffic is returned, it can be
demonstrated that the network devices and routes are still intact and
functioning.
Netcool Summary
Netcool is a fault management tool.
It is important to remember that Netcool doesn’t measure performance; it
only indicates the presence or absence of traffic from network devices
and routes.
Similar to a ping command, as long as traffic is returned, it can be
demonstrated that the network devices and routes are still intact and
functioning.