© 2015 IBM Corporation
IBM Tivoli Network ManagerBest Practices SessionITNM 3.9/4.1.1 and NCM 6.4
Rob Clark
Digital
Experience
Smarter
Process
Application
Platform
Stakeholder
Dashboards
• IT Operations• Development• Line of Business
IBM Systems Middleware
Solution Area - IT Service Management (ITSM)
Integration
IT Service
Management
Build Run Manage Optimize InnovateCapability
Solution
Area
Portfolio
Offering
Areas
Operations
Provide end-to-end insight for smarter business
decisions
Automation
More agility, with lower cost and risk
Ensure right availability of your critical business
solutions
Performance
AnalyticsProactive outage avoidance and faster problem resolution
Stakeholder
Dashboards
• IT Operations• Development• Line of Business
on-premise <----- Hybrid -----> cloud
Agenda
• Deployment with NOI
• Discovery
• Monitoring
• Events
• Administration tasks
2
Network Manager with Netcool Operations Insight
3
Standard Network Manager deployment Standard NOI 1.2 deployment
WebStart NCM
client 6.4.1
(Presentation server)
TIP 2.2 DASH
Database
Netcool Configuration
Manager 6.4.1
(Worker server)
ITNM Core
3.9 FP4 or 4.1.1
ITNM
3.9 FP4
or 4.1.1
WebGUI
7.4 FP2
TCR 2.1.1
OMNIbus 8.1
SNMP Probe
8.1
Syslog Probe
8.1
Impact
SCA-LA
TCR 3.1
WebGUI 8.1
SSO
Event Search function using SCA-LA
Reference: Integration of ITNM to NOIhttp://www.ibm.com/support/knowledgecenter/SSTPTP_1.2.0/com.ibm.netcool_ops.doc_1.2.0/omn_nmip/task/nnm_noi_ins_upgrade.html
Reference: Zane Bray’s excellent best practice documents for NOIhttp://ibm.biz/nco_bps
Panels hosted from TIP 2.2:
• All ITNM admin and op panels
• AEL from WebGUI 7.4
• All right-click context tools
• All ITNM/NCM reports from TCR 2.1.1
NCM native client launch
Cloning with VMs - Changing IP address or Hostname
• Set up one or more virtual machines as a deployment template
• Clone this for duplicate test, dev, or production environments
• Ensure each /etc/hosts is set with the new short and fully
qualified hostname
• Set new IP and hostname for each product,
• Deployment Engine, Network Manager, OMNIbus, TIP,
WebGUI, ITNM GUI, TCR, DB2, Impact, NCM
4
Reference:
http://www.ibm.com/support/knowledgecenter/SSSHRK_4.1.1/com.ibm.networkmanagerip.doc_4.1.1/itnm/ip/wip/install/task
/nmip_con_changingipaddress.html
For Impact, see: Tivoli Netcool - post deployment hostname or IP change.pdf
https://www.ibm.com/developerworks/community/files/form/anonymous/api/library/ebb177d5-dc20-4c0f-809c-
8db0401ae729/document/375d2921-b26d-4e13-af00-61580d2a4bc9/media/IBM
For NCM, see the appendix in this presentation
Discovery
Basic type – fixed seeds vs scopedDisco provisioning – who deletes the devices?Partial discoveryPrototype for enrichment
Discovery overview
© Copyright IBM Corporation 2014
Tip: select discovery mode
Fixed mode:
• Manage a definitive list of IP addresses
• Use Seed Files, split for convenience for administration• Multiple seed files will leverage multi-threading
• Scope is implied: no scope entries mean scope is implied
• Discovery Configuration GUI Advanced tab:• Disable Feedback
• Disable File Finder Verification – this will create place holder devices if ping fails (ensures device will be monitored)
Scoped mode:
• Uses scope entries as the “fence” or boundary • Missing scope entries for new devices are often the cause of devices not being discovered
• Scopes can reduce the load on large edge routers by filtering the routing table gets
• Enable Feedback on Discovery Configuration GUI Advanced tab • Will try to discover in-scope devices learned from other devices
• Use ping finder to ping spray subnets
• Useful to have seed files listing busy devices to maximize learning
• Build a seed list from a mature discovery for efficient performance• $NCHOME/precision/scripts/perl/scripts/BuildSeedList.pl
7
Reference: About discovery
http://www.ibm.com/support/knowledgecenter/SSSHRK_3.9.0/com.ibm.networkmanagerip.doc_3.9/itnm/ip/wip/disco/conc
ept/nmip_dsc_aboutdsc.html
Provisioning ITNM – verify access and credentials
Prior to provisioning ITNM with new IP addresses, run this
prototype script to verify,
• Device is responding
• SNMP credentials
After discovery,
• List all devices with no SNMP access for troubleshooting
(add –verifyAccess to retry after fixing)
• Use it to audit all or specific devices
8
Reference: Download SNMP credentials checking utility from ISM Library
http://www.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10NM0B
./itnmCheckSNMPCredentials.pl -domain ITNMDEMO -noDisco –verifyAccess –device <IP
Address>
./itnmCheckSNMPCredentials.pl -domain NCOMS -template SYSNAME, ACCESSIPADDRESS,
ACCESSINTERFACE, COMMUNITY
./itnmCheckSNMPCredentials.pl -domain NCOMS -noAccess
Partial discovery – start monitoring devices immediately
• Begin monitoring new devices before the next discovery
• Ensure IP address is in the discovery scope (if using Scope)
• Use AddNode.pl command to add new devices
– Or, select Partial Discovery in Discovery Status GUI
– Or, use OQL service disco,• insert into finders.rediscovery (m_Address) values ('172.30.100.1');
• If ncp_disco is restarted, you must first run a full discovery
• For faster discovery set in Discovery Configuration Advanced
tab,
• Disable Rediscovery Rebuild layers
– Skips recalculating the connections (tradeoff: affects RCA)
• Disable Rediscovery of Related devices
– Skips rediscovering connected devices if the connection might have
changed (tradeoff: will not attempt to update or discovery any node
learned from this device)
9
When should devices be removed?
Was it removed from the network or just down a long time? Only you can decide.
Establish one of these policies:
• Discovery should never delete anything automatically• I will decide when a device is no longer under management.
• Set default lingerTime to 1000000, and use RemoveNode.pl.– If they have not been physically removed from the network, obviously, you must adjust the
scope and seeds in disco config.
– In Fixed mode with no scope, restart ncp_disco to prevent re-pinging it from the cache
• In 3.9 - RemoveNode.pl sets the device to unmanaged and lingerTime to 0 so that the next discovery removes the device and it is no longer polled .From 4.1 - RemoveNode.pl removes the device immediately.
• Discovery should automatically remove all non-responding devices.• Usually too drastic, but useful if network undergoing significant re-IP’ing
• Devices that are temporarily down will be removed from the topology and not polled until after a future, successful, discovery.
• Set default lingerTime to 0.
• Assume device is obsolete after failing for n consecutive discoveries• Set lingerTime to 3 (default) - it will be automatically removed after failing to respond for 4
consecutive discoveries.
• To avoid surprises, use the report, "Devices pending delete on next discovery", to list all the devices that will be removed on the next discovery if they don't respond
10
Reference:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Network%20Manager/page/Discov
ery%20provisioning
Prototype: Custom Attribute Manager for ITNM 4.1.1
11
Reference: Download from the ISM Library,
http://www.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10NM0J
Custom Attribute Manager is an easy to
use wrapper to setup and manage the
attribute name-value pairs from proprietary
data.
Enrich discovery data with location, contacts, inventory, customer, lifecycle, …
Operators have the data at fingertips in Structure Browser
Use to create views for,
areas of responsibility
monitoring ranges
exporting Discovery Library Adapter (DLA) data to TADDM, TBSM
Monitoring the network
How does the Policy scope work?Managed statusAvailability polling assuranceUsing multiple pollers
Poller – Understanding Policy scopes
13
The poller will poll only the Managed
entities from this list.
Reference:
http://www.ibm.com/support/knowledgecenter/SSSHRK_4.1.1/com.ibm.networkmanagerip.doc_4.1.1/itnm/ip/wip/poll/conc
ept/nmip_poll_policyscope.html
“All Devices” or one or more views AND’d
Further reduce Device list, using filter on
device attributes
Device list further reduced by AOC class
selection
Only for interface polls - used to focus poll
on specific interfaces
Tips for Poll Definition scope filters
Class filter
• Always check the poll definition class filter for each active poll definition
• Note that new AOC classes are always unselected by default, which will unselect the parent class and thus affect its membership
14
Interface filter
• The Interface Filter incurs an overhead (based on SNMPGETs
vs the default SNMPGETNEXTs)
• Best used when it reduces the number of interfaces significantly
• When using the Interface Filter, to avoid “TooBig” error messages, add this line to NcPollerSchema.domain.cfg:
update config.properties set AggregationLimit=10;
Unmanaged status
Managed
status
Description Set by
0 Managed and polled Topology GUI, ManageNode.pl
1 Maintenance mode - not polled Topology GUI, UnmanageNode.pl
2 No status available - not polled TagManagedEntities.stch
3 IP address is not in scope –
not polled
TagManagedEntities.stch
15
• Status values 2 & 3 cannot be changed from the GUI
• Status 3 is set on IP interfaces on devices that are not in disco scope, such as
those bordering on the internet or private networks
• To set status to 1 (maintenance mode) for an interface, use the Structure
Browser
• Status is maintained in ncim.managedStatus table. Absence from this table
assumes entity is managed.
Tip: Unmanaged status
• View this stitcher to verify the rules for unmanaging interfaces
during discovery (set Status = 2)
16
$NCHOME/precision/disco/stitchers/TagManagedEntities.stch
//--------------------------------------------------------------
// Modify this statement to unmanage specific types of interface
//--------------------------------------------------------------
oqlUpdate = oqlUpdate + interfaceFilter + rediscoveryFilter +
" AND
(
ExtraInfo->m_IfDescr like 'Dialer'
OR
ExtraInfo->m_IfDescr like 'Async'
OR
ExtraInfo->m_IfDescr like 'Virtual'
OR
ExtraInfo->m_IfDescr like 'Null'
OR
ExtraInfo->m_IfDescr like 'NULL'
OR
(ExtraInfo->m_IfDescr like 'Vlan' AND IsActive <> 1)
OR
ExtraInfo->m_IfDescr like 'VLAN'
OR
ExtraInfo->m_IfAlias like 'NoMon'
)
Tip: Add IsActive <> 1 to prevent
unmanaging legitimate IP
interfaces
Availability polling assurance
Are all the IP addresses you are responsible for being pinged?
1. Upload the full list of your IP addresses
ncp_upload_expected_ips.pl
2. Take a snapshot to compare this list with the poller’s list from
the ping policies
ncp_ping_poller_snapshot.pl
3. Run the report to list the IP addresses not polled and the
reasons why
ncp_polling_exceptions.pl
17
Reference: Troubleshooting ping polling of the network
http://www.ibm.com/support/knowledgecenter/SSSHRK_4.1.1/com.ibm.networkmanagerip.doc_4.1.1/itnm/ip/wip/poll/task/
nmip_poll_troubleshootingnwpolling.html
Availability polling assurance report uncovers why an IP address is not polled
18
Undiscovered Check the scope and seed lists of the discovery
configuration.
Out of scope These IP addresses are missing from the Policy
scope for the Default Ping polls.
Unmanaged, status = 1 Devices or interfaces that have been unmanagedfrom the GUI or using the UnmanagedNode.pl
script are considered in maintenance mode and will
not be polled. They will have Status of 1.
Unmanaged, status = 2 These are unmanaged during discovery, usually inthe TagManagedEntities.stch stitcher. Check the
filter in this stitcher if it is unmanaging interfaces it
should not do.
Secondary or
Unpingable interfaces
The discovery selects the management address for
each multi-net interface with multiple IP addresses and
only those will be pinged. Network Manager does not
ping the secondary IP addresses.
What about SNMP polls?
All discovered interfacesSELECT ip.address FROM ipEndPoint ip
INNER JOIN domainMembers dm ON dm.entityId = ip.entityId
INNER JOIN domainMgr d ON dm.domainMgrId = d.domainMgrId
WHERE d.domainName = 'domainname' ORDER BY ip.address;
19
All discovered devicesSELECT ipAddress FROM mainNodeDetails m
INNER JOIN domainMgr d ON m.domainMgrId = d.domainMgrId
WHERE d.domainName = 'domainname' ORDER BY m.ipAddress;
List IP addresses from the discovered topology:
Reference: Technote: Monitoring status of chassis or interface entity
http://www.ibm.com/support/docview.wss?uid=swg21697552
What about SNMP polls? Do I have to use OQL?
• itnm_poller.pl now displays the status of all polls within the poller
• Gives visibility for both chassis and interface polls • For example
itnm_poller.pl -domain TEST -monitors ip-addresses.txt
itnm_poller.pl -domain TEST -monitors 10.101.10.10 -poller "ncp_poller(foobar)"
• Available from an APAR download described in the technote below
Multiple Pollers
Consider using 3 or more pollers as follows:
1. Admin
Designate for the administration functions for all pollers in this
domain. Use this poller to perform the MIB Grapher real-time polling
2. ICMP
Dedicate to ICMP polls. These are lightweight polls and one
poller is generally enough for the biggest networks with 5 minute
frequency.
3. SNMP
Dedicate 1 or more pollers to perform SNMP polls. These polls require
more resources for the poller. Use the poller metrics to monitor the poller
so that you can determine if you need to set up additional pollers.
20
Reference: Network Manager Best Practice Guide for Network Monitoring, Chapter 6
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Network%20Manager/page/Best%2
0Practice%20Documents
Best practices for naming poller instances
1. In CtrlServices.cfg, use this convention:• serviceName ncp_poller_ICMP
– Using the ncp prefix keeps all the core process names consistent for easy reference in ps –ef greps
• -name ICMP– This is the name shown in the Network Polling GUI
• -admin – Only one poller should be designated as admin (default)
• -noadmin– Explictly add to all other pollers
2. Register the pollerncp_poller -domain domain_name -register -name poller_name
Note:
• The default poller does not have an explicit instance name and appears in the GUI as DEFAULT_POLLER. Rename it, if you wish.
• To query the poller’s OQL tables, you will need the instance name:ncp_oql -domain NCOMS -service SnmpPoller –poller ‘ICMP’
21
Reference: Setting up an additional poller
http://www.ibm.com/support/knowledgecenter/SSSHRK_4.1.1/com.ibm.networkmanagerip.doc_4.1.1/itnm/ip/wip/admin/tas
k/nmip_adm_addpoller.html
Events
Correlating Events from 3rd party tools with topology
This Best Practice guide covers,
• Important fields for RCA and where they are set
• Includes an OMNIbus trigger you can use to check and diagnose missing
fields
• Illustrates the RCA
correlations
23
Reference: Network Manager Best Practice Guide for Event fields for enrichment and RCA
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Network%20Manager/page/Best%2
0Practice%20Documents
Pre-RCA
After RCA
Visualization
Administration tasks
Self monitoring of Network ManagerDB2 tuning for historical poll dataChanging the DB password in ITNM/NCM
General health - Monitoring health alerts
• Discovery progress and health alerts
• Poller health alerts
• Failover state changes
• ITNM process health
25
Define a filter for AEL
Include these columns in the display: LocalPriObj and LocalSecObj
NcPollerSchema.cfg Turn on poller threshold events:
update config.properties set BatchQueueThreshold = 10;
update config.properties set PollDataQueueLimit = 5000;
DiscoConfig.cfg Turn on stitcher performance events
m_CreateStchrEvents 1
Check latest discovery statistics against previous
# ncp_perl disco_profiling_data.pl -domain TIVOLI
Domain Date_of_discovery collection processing transfer total entities devices access interfaces discoMem modelMem
--------------------------------------------------------------------------------------------------------------------------------------------
TIVOLI 2014-01-27T08:26:13 00:31:21 00:06:01 00:18:51 00:56:13 33590 879 792 27830 348.85 229.42
TIVOLI 2014-01-27T10:46:24 00:31:11 00:05:54 00:08:31 00:45:36 33484 879 789 27728 344.93 232.30
TIVOLI 2014-02-04T10:18:44 00:32:28 00:05:52 00:07:18 00:45:38 33400 874 786 27662 356.15 204.64
TIVOLI 2014-02-10T08:24:58 00:31:33 00:05:50 00:06:57 00:44:20 33203 867 780 27494 354.50 204.20
TIVOLI 2014-02-10T15:55:10 00:33:36 00:05:47 00:06:49 00:46:12 33199 865 780 27494 353.05 207.20
TIVOLI 2014-03-18T10:20:55 00:32:22 00:05:54 00:07:08 00:45:24 32648 854 763 27000 363.16 207.39
TIVOLI 2014-04-16T08:49:41 00:33:53 00:05:40 02:21:42 03:01:15 32153 834 748 26578 337.61 213.90
TIVOLI 2014-05-19T07:20:50 00:43:53 00:05:19 00:52:15 01:41:27 31319 839 727 25930 325.41 212.99
TIVOLI 2014-06-03T10:20:49 00:54:29 00:05:10 00:54:26 01:54:05 31281 839 726 25901 315.39 214.99
TIVOLI 2014-06-03T11:42:20 00:52:12 00:05:11 00:56:19 01:53:42 31282 839 726 25901 325.33 216.99
TIVOLI 2014-06-03T14:39:32 00:50:14 00:05:19 01:04:08 01:59:41 31265 821 726 25901 313.39 216.99
TIVOLI 2014-06-04T07:29:25 00:42:36 00:05:19 01:06:19 01:54:14 31265 821 726 25903 308.84 217.99
TIVOLI 2014-06-04T11:10:24 00:45:12 00:05:16 00:44:38 01:35:06 31264 821 726 25901 322.79 217.99
TIVOLI 2014-06-04T13:09:21 00:43:51 00:05:19 01:05:41 01:54:51 31264 821 726 25901 323.12 217.99
TIVOLI 2014-09-03T07:11:12 00:32:23 00:04:39 02:20:12 02:57:14 30361 796 702 25096 288.01 205.64
26
If ncp_disco is not running, you can use the caches:
Reference: disco_profiling_data.pl
http://www.ibm.com/support/knowledgecenter/SSSHRK_3.9.0/com.ibm.networkmanagerip.doc_3.9/itnm/ip/wip/ref/referenc
e/nmip_ref_scriptsdiscoprofilingdata.pl.html
Reference: Monitoring network discoveries
http://www.ibm.com/support/knowledgecenter/SSSHRK_3.9.0/com.ibm.networkmanagerip.doc_3.9/itnm/ip/wip/disco/task/
nmip_dsc_monitoringnetworkdiscoveries.html
ncp_perl $NCHOME/precision/scripts/perl/scripts/disco_profiling_data.pl –domain TIVOLI \
-discocachefile $NCHOME/var/precision/Disco.Cache.disco.profilingData.TIVOLI \
-modelcachefile $NCHOME/var/precision/Model.Cache.model.profilingData.TIVOLI
Discovery – list the newly discovered devices
List devices discovered in the last 24 hours
List devices that will be removed next discovery
Send event when a chassis or interface is added or deleted,
,
27
SELECT m.entityName, m.ipAddress, m.className, dm.domainName FROM ncim.mainNodeDetails m
INNER JOIN ncim.entityData e ON m.entityId = e.entityId
INNER JOIN ncim.domainMgr dm ON m.domainMgrId = dm.domainMgrId
WHERE TIMESTAMPDIFF(8, TIMESTAMP(dm.lastUpdated) - TIMESTAMP(e.createTime)) < 24, ORDER BY
dm.domainName, m.className;
SELECT m.entityName, m.ipAddress, m.className, dm.domainName,l.lingerTime FROM ncim.mainNodeDetails m
INNER JOIN ncim.entityData e ON m.entityId = e.entityId
INNER JOIN ncim.domainMgr dm ON m.domainMgrId = dm.domainMgrId
INNER JOIN ncim.lingerTime l on m.entityId = l.entityId WHERE l.lingerTime = 0 ORDER BY dm.domainName,
m.className;
Edit $NCHOME/etc/precision/ModelSchema.cfg
Set ChassisCreationEvents, IpInterfaceCreationEvents to 1 in model.config table
Poller Metrics
1. Is the historical poll data table being maintained?
2. Is the poller successfully storing data?
3. Is the poller keeping up with the policy load at the scheduled
frequencies?
4. Is the poller's memory stable?
5. Do I need to add a new poller?
28
Reference: Network Manager Best Practice Guide for Network Monitoring, Chapter 7
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Network%20Manager/page/Best%2
0Practice%20Documents
DB tuning – Network Manager Best Practice for DB2
• Network Manager Best Practice Guide for DB2
• Configuration settings
• Tuning suggestions
• Maintenance
• Large Historical data volumes
• Set bufferpool as large as memory will hold
– Tested to 500000 (16GB) in lab
• Transaction Log settings to suit, for example,
– LOGBUFSZ =2150 (default create_db2_database.sh is 2150)
– LOGFILSIZ =15000 (default create_db2_database.sh is 5000)
– LOGPRIMARY = 10 (default create_db2_database.sh is 10)
– LOGSECOND =20 (default create_db2_database.sh is 20)
• Observed sustained and stable insert rates at around 5 million rows/hour
29
Reference: Network Manager Best Practice Guide for DB2 (Chapter 3)
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Network%20Manager/page/Best%2
0Practice%20Documents
30
Changing database passwords
• DB2 and Oracle use OS-based access accounts which often have
security regulations mandating periodic password changes.
• If not maintained properly, this will result in DB connection failures
when the password expires and can catch customers unaware.
• The readwrite database account name in use can be found in,
• $NCHOME/etc/precision/DbLogins.<domain>.cfg
• When the password is changed on the system, you must reset the
changed password in ITNM in four places:
• ITNM backend (DbLogins.cfg, MibDbLogins.cfg)
• GUI (Database Access Configuration)
• TCR BIRT & Cognos reports (trcmd.sh commands)
• Topology API for NCM (createITNMDatasource.sh)
Reference: Network Manager Best Practice Guide for DB2 (Chapter 2)
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Network%20Manager/page/Best%2
0Practice%20Documents
Appendix
Change IP/hostname for NCM
Edit the following files… ${NCM_HOME}/bin/itncm.sh
${NCM_HOME}/database/sql/ncm_insertproperties.sql
${NCM_HOME}/eWAS/profiles/RSeries/config/cells/dfltCell/nodes/dfltNode/servers/server1/server.xml
${NCM_HOME}/eWAS/profiles/RSeries/config/cells/dfltCell/nodes/dfltNode/serverindex.xml
${NCM_HOME}/eWAS/profiles/RSeries/config/cells/dfltCell/security.xml
${NCM_HOME}/eWAS/profiles/RSeries/etc/DummyClientTrustFile.jks
${NCM_HOME}/Uninstall_ITNCM/installvariables.properties
${NCM_HOME}/.installer_debug.txt
${NCM_HOME}/bin/utils/support/setWSMem.sh
${NCM_HOME}/config/properties/rseries.properties
${NCM_HOME}/config/.installed.properties
${NCM_HOME}/config/server/eventpollers.xml
${NCM_HOME}/compliance/config/server/eventpollers.xml
${NCM_HOME}/config/properties/sas.client.props
${NCM_HOME}/config/properties/ssl.client.props
${NCM_HOME}/OOBC/OutOfBandChange/run1/oobc.properties.xml
Identify the following security.xml instances, and update the hostnamels ${NCM_HOME}/eWAS/profiles/RSeries/wstemp/anonymous*/workspace/cells/dfltCell/security.xml
On TIP for ITNM integration,$NM_HOME/precision/profiles/${PROFILE_NAME}/etc/ncm/ncmjdbc.properties
32
Change IP/hostname for NCM dependencies
If other server IP/hostname changed…
DB2 hostname${NCM_HOME}/compliance/config/properties/jpa.properties
${NCM_HOME}/config/properties/rseries.properties
${NCM_HOME}/config/.installed.properties
OMNI hostname${NCM_HOME}/eWAS/profiles/RSeries/config/cells/dfltCell/wim/config/wimconfig.xml
${NCM_HOME}/config/properties/sas.client.props
${NCM_HOME}/config/properties/ssl.client.props
TIP hostname${NCM_HOME}/config/properties/sas.client.props
${NCM_HOME}/config/properties/ssl.client.props
${NCM_HOME}/eWAS/profiles/RSeries/properties/sas.client.props
${NCM_HOME}/eWAS/profiles/RSeries/properties/ssl.client.props
${NCM_HOME}/database/sql/ncm_insertproperties.sql
33
Notices and Disclaimers
Copyright © 2015 by International Business Machines Corporation (IBM). No part of this document may be reproduced or
transmitted in any form without written permission from IBM.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM.
Information in these presentations (including information relating to products that have not yet been announced by IBM) has been
reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM
shall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY,
EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OF
THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT
OR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of the
agreements under which they are provided.
Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without
notice.
Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are
presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual
performance, cost, savings or other results in other operating environments may vary.
References in this document to IBM products, programs, or services does not imply that IBM intends to make such products,
programs or services available in all countries in which IBM operates or does business.
Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not
necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither
intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.
It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal
counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s
business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or
represent or warrant that its services or products will ensure that the customer is in compliance with any law.
Notices and Disclaimers (con’t)
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products in connection with this
publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to
interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.
The provision of the information contained herein is not intended to, and does not, grant any right or license under any
IBM patents, copyrights, trademarks or other intellectual property right.
• IBM, the IBM logo, ibm.com, Bluemix, Blueworks Live, CICS, Clearcase, DOORS®, Enterprise Document
Management System™, Global Business Services ®, Global Technology Services ®, Information on Demand,
ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™,
PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®,
pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, SoDA, SPSS, StoredIQ, Tivoli®, Trusteer®,
urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of
International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and
service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on
the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.
Thank YouYour Feedback is
Important!
Access the InterConnect 2015
Conference CONNECT Attendee
Portal to complete your session
surveys from your smartphone,
laptop or conference kiosk.
IT Operations Management: Expo Zone Presence
• Mandalay Bay Expo Hall – Cloud Infrastructure & IT Optimization Zone, ‘Manage IT Like a Super Hero’
• See IT Operations Management Solutions In Action at the Pedestal Stations
– 810-01, Innovative Analytics for increased operations efficiency
– 810-02, Transformative Analytics drives faster incident reduction
– 810-03, Avoid IT outages; Diagnose faster with all operational data
- Fun Games & Prizes: Visit a Ped, Get a Gold Coin to play a Game to Win a Prize
- Gain Visibility in a game of Oculus Rift
- Gain Control with Giant Jenga
- Use Automation to build Rube Goldberg Device
- #ITSuperHero
- Super Hero Photo Booth & Participation Prize
- Share photos on Twitter with #SaaSHero for a chance to win a daily prize
37
Communities, Social, & References
• On-line communities, User Groups, Technical Forums, Blogs, Social networks, and more
o Find the community that interests you …
• http://Servicemanagement360.com
o Follow @servicemgmt @IBMTivoli and use hashtags#ibminterconnect #Netcool #ITSuperhero, #SaaSHero, #ITSM
o Visit the InterConnectGo Social Lounge for interactive activities
o Learn More on the Web: https://www.ibmserviceengage.com/it-operations-management/learn
38
Operations Management – Top Sessions
39
Date Time Room Session Title Session type
2/23 8:30-10:00 MGM Grand Arena 6043A A New Way to Think General Session
2/23 2:00-3:00 MB - Lagoon I 1331 Operations Management Trends and Directions Operations Management
2/23 3:30-4:30 MGM Grand Ballroom 6412 Accelerating Hybrid with Cloud Infrastructure and IT Optimization Cloud & IT Optimization Stream
Keynote
2/23 5:00-6:00 MB - Breakers D 2933 CSP Business Transformation and the Evolution of NOC to SOC:
Track Kickoff with Alcatel-Lucent
Operations Management
2/24 9:30-10:30 MB - Lagoon I 5805 Come hear how Clarnet reduced routine events by an additonal
46% by leveraging Event Analytics
Operations Management
2/24 9:30-10:30 MB - Islander F 5926A Hybrid Collaborative Service Management—Have Your Cake
and Eat It, Too!
Operations Management
2/24 11:00-noon MB - Breakers D 2779 IBM Tivoli NetCool - the main driver for MegaFon GNOC
transformation
Operations Management
2/24 11:00-noon MB - Lagoon I 5613 Business and Operational Efficiency with Automated Service
Creation and Sharing
Operations Management
2/24 1:30-1:50 MB : EXPO 6798A Collaborative Ops for a Hybrid World Operations Management
2/24 2:30-3:30 MB - Lagoon I 1348 C&SI's Operations Management Roadmap/Analytics-driven Fault
Management
Operations Management
2/24 3:30-5:15 MGM Grand Arena 6098A A New Way to Work General Session
2/24 5:30-6:30 MB - Lagoon I 3378 CenterPoint Energy's Return On Investment Using the Netcool
Suite
Operations Management
2/25 1:00-1:20 MB : EXPO 6798B Collaborative Ops for a Hybrid World Operations Management
2/25 2:00-3:00 MB - Lagoon I 3565 IBM Alert Management: Helping Organizations to Meet SLAs Operations Management
2/25 3:30-5:00 MGM Arena 6101A A New Way Forward General Session
2/25 3:30-4:30 MB - Mandalay
Ballroom A
5926B Hybrid Collaborative Service Management—Have Your Cake
and Eat It, Too!
Operations Management
2/25 5:30-6:30 MB-Breakers D 1540 How C&SI Teams Achieved IT Operational Efficiencies Using
Netcool Operations Insight
Operations Management
2/26 1:00-2:00 MB - Breakers F 1540 How C&SI Teams Achieved IT Operational Efficiencies Using
Netcool Operations Insight
Operations Management