Netcool/RAD 3.0 References
** If you’re interested in anything mentioned on this page, please feel free to contact me directly or leave a comment. I will update this page with more information, content, etc. as I have time to complete things mentioned here. If you’re interested in official engagements with me, feel free to contact your account team or myself directly as well. **
– Search this blog’s postings via the TAG clouds along the sidebar.
Netcool/RAD 3.0 Information
Netcool/RAD 3.0 Support
Netcool/RAD 3.0 Support Forum Search
Current Documentation (no login required)
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_rad.doc/welcome.htm
Current and Legacy Documenation (requires login)
Netcool/RAD 3.0 Admin Guide
Netcool/RAD 3.0 Scenarios Guide
Netcool/RAD 3.0 Service Configuration Guide
Netcool/RAD 3.0 Customization Guide
Netcool/RAD 3.0 Release Notes
Netcool/RAD 3.0 & NGF
Integrating ITCCMDB CDTS/CMDB/TADDM GUI into NGF
Netcool/RAD 3.0 and TBSM 4.1 Best Practices, How To and Field Guides:
Netcool/RAD 3.0 and TBSM 4.1 Best Practice, How To and Field Guides
Important Concepts
Templates
Instances
Policies
Rules
Canvas
Service Navigator
SLA
Dependencies
RAD Shell API
Data Fetchers
External Service Dependency Adaptor (ESDA)
Event Reader
URL Hacking – ServeViewerApplet, GetSnapshot, &Options, Turning off menu toolbars
NGF Pages/Viewpoints/Tabs,etc.
Actions, Sticky Transition “bug”, use of IFrame for ServiceTree-ServiceViewer
Custom TreeTemplates and how to view
CustomCanvas, CustomView, View Definitions
Netcool/RAD 3.0 Services Offerings
BSM Methodology Workshop
Service Modeling Concepts
BPM integration
ITCCMDB/CDTS/TADDM Integration
Other CMDB/Inventory Integration (BMC/Remedy Atrium, etc.)
Netcool/RAD 3.0 Support
————————
What to collect before opening a PMR for a Netcool/RAD 3.0 issue. Doing these things should greatly increase the speed of getting a meaningful response from support.
Preparing for opening a PMR with IBM for Netcool/RAD
———————————————————————————————-
**
** Note:
**
** When collecting logfiles and information for support, it is extremely helpful to capture the system time range for when the problems were noticed to aide in logfile parsing.
**
** Limit/cease the use of all other programs, browsers, clients, etc when doing the revalidation and collection of information for support.
**
Netcool/RAD Logs
———————————
tar cvf serverlogs.tar RAD_HOME/log
tar cvf ncsmlogs.tar NCSM_HOME/log
tar cvf guifoundationlogs.tar RAD_HOME/guifoundation/logs
tar cvf omnibuslogs.tar $OMNIHOME/log (if OMNIbus is suspect)
Data Collection
—————————-
The output of $RAD_HOME/bin/rad_server -version
The output of OMNIbus $OMNIHOME/bin/nco_objserv -version
Approximately how many events are normally resident in the object server (all events, not just the ones effecting RAD services)?
Approximately how many events are being scanned by RAD for service instances (how many events are matching your instance rules, or the ones that you think are causing problems)?
A screenshot of the errors seen in the browser (control + print screen) or detailed description of what is seen.
How many simultaneous users are logged in? Output of netstat -na | grep [rad port] | wc -l
System Information
———————————
Hardware platform (Make/Model/CPU/Memory/Disk)
Operating system (Version, Revision, Patch Level)
Disk utilization – output of df -k and du -h
Memory Utilization – output of cat /proc/meminfo and output of free command
Files open – output of lsof
What sort of load is the box carrying? What do you see in the output of ‘top’ when you see the problem occurring?
Client Information
————————
Hardware platform (Make/Model/CPU/Memory/Disk)
System Information – Run C:\Program Files\Common Files\Microsoft Shared\MSInfo\msinfo32.exe – select file and export all of the contents from this program. Save as clientsystemconfig.txt.
Java Environment – output of java – version run in a command window
Turn on the Java Console (in browser – Tools – Sun Java Console) : Collect the logs from the Java Console during the time range that you’ve experienced the problems
Enhanced Backup and Restoral Options
————————————–
I’ve been collecting notes, tips and tricks on what should be backed up and how within Netcool/RAD. Here are a few pointers.
Modifiying the RAD_DB Script For a Full Database Backup
By default, the $NCHOME/rad/bin/rad_db script backup option only executes a backup of the data within the internal Postgres database by using the -a option for the pg_dump command. Removing this flag will allow for a complete database dump with all table creation parameters to be created. THIS IS CRITICAL IF YOU HAVE CREATED ANY CUSTOM TABLES IN THE INTERNAL POSTGRES DATABSE OR ARE USING IT FOR ANY OF THE DEMOS.
**Note: Data Sources and Data Fetchers are not stored in the database. Use of the rad_radshell export (); command will still be required to export those configurations.
I’ve modified my rad_db script as shown below so I now have a “fullbackup” option via the command line.
fullbackup)
if [ -z “$BACKUPFILE” ]; then
DATE=`date +%Y%m%d_%H%M%S`
BACKUPFILE=”${RAD_HOME}/tmp/rad_db_backup_${DATE}”
else
if [ -f “$BACKUPFILE” -a ! “$FORCE” = “1” ]; then
err “Full Backup file ‘”$BACKUPFILE”‘ already exists”
fi
fi
>$BACKUPFILE 2>/dev/null
if [ ! $? = 0 ]; then
err “Cannot write to full backup file ‘”$BACKUPFILE”‘”
fi
db_status
if [ $? = 0 ]; then
err “Database not running”
fi
myecho “Dumping Full Database Schema and Data …”
case “$NCSDB_TYPE” in
postgres*)
# -D -> dump data as INSERT commands with attribute names
# -C -> output commands to create database
# -c -> clean (drop) schema prior to create
# -n -> suppress most quotes around identifiers
# -a -> dump out only the data, not the schema
# egrep -> Skip the trigger locking, specific to Postgres
#${PGHOME}/bin/pg_dump –help
#exit
# had to remove -c and -n because not supported on postgres 7.3.1 (SDP 07-Feb-03)
${PGHOME}/bin/pg_dump \
-D -h “${NCSDB_HOST}” -p “${NCSDB_PORT}” “${NCSDB}” \
| egrep -v “(\\connect |pg_class.*trigger|^–.*trigger)” \
> $BACKUPFILE
;;
esac
echo “done.”
echo
echo “The full backup file can be found at ‘”$BACKUPFILE”‘”
;;