BRKNMS 2000

Using CiscoWorks LMS to its full potential
BRKNMS-2000 Jose Moreno (josemor@cisco.com)
BRKNMS-2000
2009 Cisco Systems, Inc. All rights reserved.
Cisco Public
Using CiscoWorks LMS to its full potential - Agenda

1 Introduction scope definition 2 Integrating LMS into the NMS landscape 3 Configuration Management with LMS 4 Fault Management with LMS 5 Performance Management with LMS 6 Where to go next?
BRKNMS-2000
Cisco Public
Housekeeping
We value your feedback- don't forget to complete your online session evaluations after each session & complete the Overall Conference Evaluation which will be available online from Thursday Visit the World of Solutions Please remember this is a 'non-smoking' venue! Please switch off your mobile phones Please make use of the recycling bins provided Please remember to wear your badge at all times including the Party
3
BRKNMS-2000
Cisco Public
Introduction Scope Definition
BRKNMS-2000
Cisco Public
Abstract
In this breakout session we will discuss how to use some not-sowell-known features of CiscoWorks LAN Management Solution (LMS), to improve the integration with other Management Systems, and to enhance the automation of certain tasks, reducing the manpower required to operate a corporate network. Among the features to be discussed are integration capabilities of Common Services, interaction between LMS components and external tools like TACACS+ Servers, cabling databases or Configuration Management Databases (CMDB), compliance management verifications that can be run with Resource Management Essentials (RME) , or automating tasks using in an orchestrated manner different LMS components with advanced IOS features like Embedded Event Manager (EEM) and IP SLA.
BRKNMS-2000
Cisco Public
What this session IS about

Use cases description Suggestions of not-so-well-known features Exchange of customer experiences
What this session is NOT about

Description of LAN Management Solution (LMS) components In-depth tutorial Exhaustive feature listing
BRKNMS-2000 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
Glossary
ACL: Access Control List CIC: Cisco Info Center CLI: Command Line Interface CM: Campus Manager CMDB: Configuration Mgmt Database CS: Common Services CS ACS: Cisco Secure Access Control Server CSM: Cisco Security Manager DCR: Device Credential Repository DFM: Device Fault Manager EEM: Embedded Event Manager EOT: Enhanced Object Tracking GOLD: Generic OnLine Diagnostics HSRP: Hot Standby Router Protocol HUM: Health and Utilization Monitor IPM: Internetwork Performance Monitor ISP: Internet Service Provider LMS: LAN Management Solution MoM: Manager of Managers NMS: Network Management System ODBC: Open Database Connection QoS: Quality of Service RME: Resource Manager Essentials SLA: Service Level Agreement TDR: Time Domain Reflectometry VPN: Virtual Private Network UT: User Tracking UTU: User Tracking Utility
Sorry for the TLAs!

The FCAPS model

What is management? Fault mgmt Config mgmt Accounting Performance Mgmt Security Mgmt
http://www.iec.org/online/tutorials/ems/topic03.asp http://en.wikipedia.org/wiki/Fcaps
Integrating LMS into the NMS landscape
BRKNMS-2000
Cisco Public
Is integration important?
Integration capabilities are the most valued item in management tools If a tool is not correctly integrated, it will consume too many resources That is exactly the opposite target of Network Management
BRKNMS-2000
Cisco Public
10
What other tools typically exist out there?

TACACS+/RADIUS Server (CiscoSecure Access Control Server) Fault Management Umbrella (HP OpenView, Cisco Info Center, NetCool, etc) Other CiscoWorks-based tools
CiscoWorks Cisco Security Manager (Security) * CiscoWorks Quality of Service Policy Manager (QoS) CiscoWorks Operations Manager (Voice)
Configuration Management Database (CMDB) Other documentation databases

Cabling You name it
11
Integration with CS ACS (i)

Problem definition: 1.Users already defined in the TACACS+ server 2.Usually, users permissions (authorization) is configured there as well 3.Devices must be added to both CiscoWorks LMS and CS ACS (Access Control Server) 4.CS ACS does not have device discovery capabilities: manual addition of devices
BRKNMS-2000
Cisco Public
12
Integration with CS ACS (ii)

Integration benefits:
Granular and simplified privilege management Single-point of configuration for user attributes (CS ACS) Consistent configuration
Out-of-the-box integration:
Authentication & Authorization for users in CS ACS
Further integration: Device Credentials Repository device synchronization Example (DOS Batch File):
@echo off set DCRCLIFILE=C:\dcrclifile.txt C:\"Program Files"\CSCOpx\bin\dcrcli -u lmsadmin cmd=expAcs hn=acs-munsec un=csadmin prt=2002 proto=http seckey=cisco ndg=new_devices_from_lms
13
BRKNMS-2000
Cisco Public
Integration with Fault Management Manager-of-Managers (MoM)

Out-of-the-box integration with 3rd party NMS Tools: HP OpenView or NetView Trap forwarding out of Device Fault Manager (DFM) Trap forwarding out of Health and Utilization Monitor (HUM) syslog2trap
BRKNMS-2000
Cisco Public
14
CiscoWorks Integration Utility

Out-of-the-box integration with HPOV 7.51 and NetView 7.1.5 CiscoWorks Application (CiscoView) Cisco Alarms-appearing after integration HPOV Panner Cisco Icon
More Info (v1.7): http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services _software/3.1/user/nmim/guide/nmimug.html 15
2009 Cisco Systems, Inc. All rights reserved. Cisco Public
BRKNMS-2000
Fault management architecture with DFM

DFM can perform a device-level event correlation for supported events Other events are passed-through There are other applications specialized in network-level event correlation, like Cisco Information Center (CIC) Example:
Router B
No t re ach abl e
Cisco Info Center Problem with A

ble a ch th A a e wi tr o m B n roble P
16
Router A
High temperature Not reachable
DFM
BRKNMS-2000
Cisco Public
Send traps out of syslog messages (i)

Problem description: 1.The enterprise/network event management system can only process SNMP traps, not syslog messages. 2.There are no SNMP traps configured for certain events, depending on the platform and software (for example, routing protocol adjacencies)
RME DFM Cisco Info Center
Syslog
No info about the event!
BRKNMS-2000
Cisco Public
17
Send traps out of syslog messages (ii)

Solution description: LMS can trigger SNMP traps upon reception of Syslog messages
RME: Tools Syslog Automated Actions Trap sending software: open source tools, for example, http://www.net-snmp.org
Cisco Info Center
RME
DFM
Syslog
Trap
Trap
BRKNMS-2000
Cisco Public
18
Send traps out of syslog messages (iii)

C:/Program Files/CSCOpx/files/scripts/syslog/sys2trap.bat (Windows)
@echo off set logfile="C:\sys2trap.log" echo **************************** >>%logfile% date >>%logfile% time >>%logfile% echo Trap sent to %1, message: %2 >>%logfile% echo **************************** >>%logfile% snmptrap -v 2c -c public 1.1.1.1 '' '' 1.3.6.1.4.1.9.9.41.2 s "OSPF!"
Solaris: /var/adm/CSCOpx/files/scripts/syslog
BRKNMS-2000
Cisco Public
19
Send traps out of syslog messages (iv)

Before reinventing the wheel: SNMP support for events is more and more extensive On some IOS versions you have now the command snmp-server enable traps syslog Many event managers are able to process syslog messages as well as SNMP traps/informs
BRKNMS-2000
Cisco Public
20
Other CiscoWorks tools (i)

Problem definition: 1.If "n" Common-Services (CS) based tools are in production, you do not want "n" discovery processes running, or to have to manually add "n" times the same device For example: Cisco Security Manager, QoS Provisioning Manager, Operations Manager
BRKNMS-2000
Cisco Public
21
Other CiscoWorks tools (ii)

Solution description: 1.Configure Device Credentials Repository (DCR) Synchronization between your CS-based tools: one master will perform the discovery, and the slaves will get the results automatically 2.Make sure the highest Common Services version is the master!
BRKNMS-2000
Cisco Public
22
Integration with CMDB (i)

Problem description: 1.ITIL mandates the existence of a Configuration Management Database (CMDB), to document all IT Systems 2.Multiple vendors offer CMDB Systems, some customers grow their own. 3.These CMDB Systems usually have no network discovery capabilities: devices must be manually added 4.Eventually, discrepancies between CW LMS and the CMDB will pop up
BRKNMS-2000
Cisco Public
23
Integration with CMDB (ii)

Industry approaches: 1.I want a CMDB that reflects exactly what my network actually looks like, and dynamically learns any change: The CMDB imports the info out of CiscoWorks LMS 2.I want a CMDB that describes what my network should look like. Any discrepancy should be reported: The CMDB controls the addition/deletion of devices into CiscoWorks LMS
24
BRKNMS-2000
Cisco Public
Integration with CMDB (iii)

DCR integration (dcrexport.bat):
set DCRCLIFILE=C:\dcrclifile.txt C:\PROGRA~1\CSCOpx\bin\dcrcli -u lmsadmin cmd=exp fn="C:\Documents and Settings\Administrator\My Documents\DEE\dcrexport.xml" ft=xml
XML output can be reformatted to the XML format expected from your Database with Extensible Stylesheet Language Transformations (XLST): http://en.wikipedia.org/wiki/Xslt You can use your Web Browser or any other XML viewers to verify the output
BRKNMS-2000
Cisco Public
25
Integration with CMDB (iv)
BRKNMS-2000
Cisco Public
26
Integration with CMDB (v)

RME integration (extracting info):
DEE.bat
perl DEE.pl http://localhost:1741/rme/cwcli %1.xml
DEE.pl (post-request)
http://<your-lmsserver>:1741/help/rme/fundamentals/cwcli_Runing_cwcli_inventry_getdevicestate_Cm d.html#wp1111935
XML Payload for device inventory export (exportinventory_DIST1.xml)

<payload> <command>cwcli export inventory -u lmsadmin -p Y2lzY28= -device DIST1</command> <arg></arg> <arg-val></arg-val> </payload>
Everything together:
dee exportinventory_DIST1
BRKNMS-2000
Cisco Public
27
Integration with CMDB (vi)

How to parse XML data? XSL Transforms: http://en.wikipedia.org/wiki/Xslt Simple API for XML (SAX): http://en.wikipedia.org/wiki/Simple_API_for_XML DOM Parser: XML DOM object that can be accesses with JavaScript. http://www.w3schools.com/Dom/dom_parser.asp XML::Simple (Perl): http://search.cpan.org/~grantm/XML-Simple2.18/lib/XML/Simple.pm
28
Integration with generic databases (i)

Problem definition: 1.Enterprises often deploy custom databases for documentation purposes. For example, for cabling information 2.The cwcli-based solution might not be performant enough for real-time access to these databases
BRKNMS-2000
Cisco Public
29
Integration with generic databases (ii)

Solution description: 1.You can access to every LMS piece of information through an ODBC interface 2.The LMS database is SQL Anywhere 3.Please note that ODBC access to LMS might have some security implications (admin access to DB) 4.LMS DB Schema not public! 5.Please note that ODBC access to LMS is not supported by TAC
BRKNMS-2000
Cisco Public
30
Integration with generic databases (iii)

ODBC Data Source Configuration (Adaptive Server Anywhere 9.0 ODBC driver) Resetting your LMS password might be required ODBC attributes files (Windows & Solaris):
CSCOpx\databases\ani\orig\odbc.tmplorig
BRKNMS-2000
Cisco Public
31

BRKNMS-2000
Cisco Public
32

BRKNMS-2000
Cisco Public
33

BRKNMS-2000
Cisco Public
34

BRKNMS-2000
Cisco Public
35
Integration with generic databases (iv)

Example: integration with a Microsoft Access database
BRKNMS-2000
Cisco Public
36
Integration with generic databases (v) (screenshots for your reference)
BRKNMS-2000
Cisco Public
37
Integration with Web-based tools (i)

Problem definition: 1.Enterprises often deploy a number of tools (usually Web-based), for management purposes 2.These tools might refer to network devices, and direct access from these tools might save a lot of time For example: a server management tool tells you that server XYZ is not reachable any more, quoting as likely problem its default gateway
BRKNMS-2000
Cisco Public
38
Integration with Web-based tools (ii)

Solution description: 1.Some Web-based tools can be customized to include external links 2.These links can refer to specific components of CiscoWorks LMS
For example: CiscoView: http://<lms_server>:1741/CVng/chassis.do?deviceip=<device> Device Center: http://<lms_server>:1741/cwhp/device.center.do?device=<device>
BRKNMS-2000
Cisco Public
39
Configuration Management
BRKNMS-2000
Cisco Public
40
What is Configuration Management?

Access to configuration information
Configuration files / features Hardware inventory Software inventory
Analysis of that information

Compliance reporting Vulnerability checks Proactive troubleshooting
Remote configuration and provisioning
BRKNMS-2000
Cisco Public
41
Compliance Management (i)

Problem definition: 1.I have internal or external network standards 2.I am not sure, if my devices are compliant with my standards
BRKNMS-2000
Cisco Public
42
Compliance Management (ii)

Solution description: 1.With baseline templates you can define what your network standards are 2.RME will periodically check which devices are not in compliance, and suggest you the required changes to regain compliance How fit are you with regular expressions? Just google for "regexp tutorial", or check
http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html
BRKNMS-2000
Cisco Public
43
Compliance Management (iii)

Common use cases:
No public/private community strings
- snmp-server community [#(public|private) R[OW] .*#]
SSH-only access
[#line vty .*#] + transport input ssh
Static multicast RP definitions consistent

+ ip pim rp-address 1.1.1.1 override
Security policies (service password-encryption, etc)

+ service password-encryption
Disabling CDP in certain interfaces
BRKNMS-2000
Cisco Public
44
Compliance Management (iv)
BRKNMS-2000
Cisco Public
45
Shadow directory: finding info (i)

Problem definition: 1.Problem ticket: user with IP 192.168.19.43 cannot connect to SAP server 172.16.115.2 on TCP ports 3300 to 3600 2.The operator needs to answer these questions as soon as possible:
Subnet mask for both systems Default gateway for both systems Is anywhere in the network an ACL in place? Is anywhere in the network routing redistribution in place? Is anywhere in the network routing filtering in place?
46
Shadow directory: finding info (ii)

Solution description. 2 alternatives: 1.Search the LMS config archive (recommended)
Quickly get the required info For simple queries, the CiscoWorks Assistant might be more effective
2.Search the shadow directory

You can create a shell script to make shadow directory searches quicker (a sequence of greps in the different directories) Note you search only the latest config version Requires shell access to the LMS station: security issue?
BRKNMS-2000
Cisco Public
47
Shadow directory: finding info (iii)

What is the shadow directory?
A directory where the latest device configs are stored
How to enable it?

RME Config Mgmt Archive Mgmt Archive Settings
Where to find it?

/var/adm/CSCOpx/files/rme/dcma/shadow NMSROOT/files/rme/dcma/shadow
48
Shadow directory: finding info (iv)

Sample UNIX script:
#!/usr/bin/sh /usr/bin/grep Rl %1 /var/adm/CSCOpx/files/rme/dcma/shadow/*
Sample Windows script:

@echo off findstr /S /C:%1 C:\Progra~1\CSCOpx\files\rme\dcma\shadow\*
Tip: sed for Windows (http://gnuwin32.sourceforge.net/packages/sed.htm)

@echo off findstr /S /C:%1 C:\Progra~1\CSCOpx\files\rme\dcma\shadow\* ^ | C:\GnuWin32\bin\sed.exe "s/C\:\\Progra~1\\CSCOpx\\files\\rme\\dcma\\shadow\\//"
BRKNMS-2000
Cisco Public
49
Shadow directory: finding info (v)

Example: where do I have IP address 10.1.4.1 configured? Which mask does it have?
C:\Documents and Settings\Administrator\My Documents> config "address 10.1.4.1 " Routers\PRIMARY\c7507.cfg: ip address 10.1.4.1 255.255.255.255 C:\Documents and Settings\Administrator\My Documents>
Example: which devices have default routes in my network?

C:\Documents and Settings\Administrator\My Documents> config "route 0.0.0.0" Routers\PRIMARY\c7507.cfg:ip route 0.0.0.0 0.0.0.0 10.49.216.2 C:\Documents and Settings\Administrator\My Documents>
BRKNMS-2000
Cisco Public
50
Shadow directory: exposing configs (i)

Problem definition: 1.Application people need easy and uncomplicated access to the configs of the network load balancers 2.Sensitive information should be removed from the published configs
BRKNMS-2000
Cisco Public
51
Shadow directory: exposing configs (ii)

Solution description: 1.Device configurations can be periodically exported from the shadow directories to a shared folder (NFS / CIFS / HTTP) 2.Before exporting the configs, sensitive information like SNMP community strings or passwords can be grepped out
BRKNMS-2000
Cisco Public
52
Shadow directory: exposing configs (iii)

Removing sensitive information from a config file UNIX:
DestDir=/export/safeconfigs/ backupdir() { dir=$1 # Generate a list with the files in that directory filelist=`/bin/ls -1 $dir` /usr/bin/cd $dir # For every configuration file for file in $filelist do srcfile=$dir$file dstfile=$DestDir$file /usr/bin/grep -v pass $srcfile | /usr/bin/grep -v secret | /usr/bin/grep -v community | /usr/bin/grep -v username >$dstfile done } backupdir /var/adm/CSCOpx/files/archive/shadow/Cisco_Router/ backupdir /var/adm/CSCOpx/files/archive/shadow/Cisco_Catalyst_Switch/ backupdir /var/adm/CSCOpx/files/archive/shadow/Cisco_Catalyst_IOS_Switch/ backupdir /var/adm/CSCOpx/files/archive/shadow/Cisco_Content_Service_Switch/
Windows: findstr /V
53
Shadow directory: exposing configs (iv)

Exporting configs to another server: 1.Remove sensitive info (see previous slide) 2.Copy over the "safe" config files to a directory in the new server serviced by the Web server of your choice (Apache?) 3.Dynamically create an HTML index page with links to all the config files
BRKNMS-2000
Cisco Public
54
Shadow directory: exposing configs (v)

Dynamically creating an index page (for your reference)
# Open input (list with config files) and output (html page to be # generated) files $in=$ARGV[0]; $out=$ARGV[1]; open(LST,$in); @files=<LST>; close(LST); open(NDX,">$out"); # Insert the first code in the html, constant for all pages printf NDX "<html>\n"; printf NDX "<head>\n"; printf NDX "<meta http-equiv='Content-Type' content='text/html; charset=iso-8859-1'>\n"; printf NDX "<meta name='author' content='Jose Moreno'>\n"; printf NDX "<title>Configuration files stored in the LMS Server</title>\n"; printf NDX "</head>\n"; printf NDX "<body background='square.gif' bgcolor='#FFFFFF'>\n"; printf NDX "<h1>Configuration of devices downloaded by CiscoWorks LMS</h1>\n"; printf NDX "<p>The following files are UNIX text files, so they should be open with Windows Wordpad</p>\n"; printf NDX "<ul>\n"; # Analyze the config files list line per line foreach $file(@files) { # Print one link per config file. The following line tries to separate # the filename from the rest of the path. if ($file=~/.*\/([\w-_.]*)$/) { $file=$1; printf NDX "\t<li><a href='./$file'>$file</a></li>\n"; } } # Print the last html statements to finish the html page printf NDX "</ul>\n"; printf NDX "</body>\n"; printf NDX "</html>\n"; # Close the output file close(NDX);
BRKNMS-2000
Cisco Public
55
Fault Management
BRKNMS-2000
Cisco Public
56
What is Fault Management?

Quickly and easily detect, isolate, and correct network faults:
Monitor not only up and down status, but also potential problems Provide valuable insight into the relative health of a device and the network Address problems before network service degradation impacts users
Minimize downtime and service degradation
BRKNMS-2000
Cisco Public
57
Function definition
LMS fault management mission statement:
Help proactively detect incidents, before they become problems Detect network events and correlate them at device-level for Cisco devices Forward the consolidated alerts to generic fault management systems
BRKNMS-2000
Cisco Public
58
DFM fine tuning: managed ports (i)

Per default, DFM monitors only trunk ports and routed ports Access ports (non-routed, non-trunk) connected to network devices are also important, and therefore should be managed You can configure these ports in a way that DFM manages them (polls them and process up/down traps)
BRKNMS-2000
Cisco Public
59
DFM fine tuning: managed ports (ii)

Assign ports to customizable groups, and then configure the desired polling / thresholds settings
BRKNMS-2000
DFM Configuration Other Configurations Group Administration

2009 Cisco Systems, Inc. All rights reserved. Cisco Public
DFM Configuration Polling and Thresholds Managing Thresholds
60
DFM fine tuning: 2-level polling (i)

You can probably divide your devices in at least 2 groups:
Standard Critical
Polling/thresholds/notifications would look different for a core router than for an access switch in a branch You can use DFMs Customizable Groups to configure different polling attributes and thresholds for your devices Group membership can be based on different attributes, for example a string in the device name
61
DFM fine tuning: 2-level polling (ii)

Assign your critical devices to a new customizable group, and modify its polling / threshold settings
BRKNMS-2000
Cisco Public
62
Fault mgmt with Campus Manager (i)

CM-DFM integration: in Campus Manager you see on LMS 3.1 and above whether alarms have been triggered by Device Fault Manager for the devices shown (red/green management)
BRKNMS-2000
Cisco Public
63
Fault mgmt with Campus Manager (ii)

User defined views: you can create custom views, based on different variables like hostname or IP address, or static assignments Hierarchical maps (nested views) can be used for troubleshooting drill-down
BRKNMS-2000
Cisco Public
64
Fault mgmt with Campus Manager (iii)

Already spent half an hour trying to figure out root, designated, forwarding and blocking ports? Campus Manager Topology Services STP View can help out here!!
BRKNMS-2000
Cisco Public
65
End-user connectivity troubleshooting (i)

Problem definition: Helpdesk operators spend too much time finding out relevant troubleshooting information when users open a service request Solution Description LMS will correlate relevant end-device information from different sources (switches, routers, DNS, etc) and present it consolidated to the Helpdesk operator
BRKNMS-2000
Cisco Public
66
End-user connectivity troubleshooting (ii)

User Tracking is your friend!! Some tips: Try out the Windows task bar (User Traking Utility, UTU) if you get frequent end-user problem tickets Consider installing UTLite.exe on your Windows end hosts, if the logged user information is relevant in order to identify the end-system Alternatively you usually need to rely on users telling you his/her PC name If you have no user on the phone to talk to, how are you going to find out PC name / whom to call?
67
End-user connectivity troubleshooting (iii)

Sample User Tracking report:
BRKNMS-2000
Cisco Public
68
End-user connectivity troubleshooting (iv)

With the User Tracking Utility, now it is even easier finding troubleshooting information about your end systems!
BRKNMS-2000
Cisco Public
69
Get your discrepancy info out of Campus Manager (i)

Problem definition: Users are not automatically notified wherever a discrepancy is found, so discrepancies are not fixed as quick as they should Solution description: Campus Manager can notify your generic Fault Management System of configuration discrepancies, by means of Syslog messages
BRKNMS-2000
Cisco Public
70
Get your discrepancy info out of Campus Manager (ii)

Discrepancies Reports (portal and full versions)
BRKNMS-2000
Cisco Public
71
Get your discrepancy info out of Campus Manager (iii)

Configuration: Campus Manager Admin Other Admin Settings Discrepancies Configure
BRKNMS-2000
Cisco Public
72
How about a "self-healing network"? (i)

Problem definition: a network problem makes my devices lose connectivity to the management station (for example, wrong ACL, wrong interface shut, etc). Solution description: I need some intelligence in the device able to recover from the problem
BRKNMS-2000
Cisco Public
73
How about a "self-healing network"? (ii)

With EEM you can configure typical "trigger-action" rules that your network devices will be able to run Those rules or policies can be of two types:
Applets: actions are stored in the configuration file Scripts: actions are stored in flash
For example:
"if you lose connectivity to servers/routers A, B and C" Then "Reload"
BRKNMS-2000
Cisco Public
74
EEM Applet Example Connectivity Failure Detection

IP SLA
ip sla 10 icmp-echo 3.3.3.3 timeout 500 frequency 3 ip sla schedule 10 life forever start-time now
Enhanced Object Tracking (EOT)

track 100 rtr 10 reachability delay down 10 up 20
Email server
Environment Variables
event manager environment _email_server 172.27.121.177 event manager environment _email_from router@xyz.com event manager environment _email_to attach@cisco.com IP SLA/EOT/EEM
email
EEM Applet (a)

event manager applet LMS_unreachable event track 100 state down action 1.0 syslog msg "Ping has failed, LMS unreachable!" action 1.1 cli command "enable" action 1.2 cli command "del /force flash:LMS_unreachable" action 1.3 cli command "show clock | append LMS_unreachable" action 1.4 cli command "show ip route | append LMS_unreachable" action 1.5 cli command "more flash:LMS_unreachable" action 1.6 mail server "$_email_server" to "$_email_to" from "$_email_from \ subject "LMS Unreachable: ICMP-Echos Failed" body "$_cli_result" action 1.7 syslog msg "LMS unreachable alert has been sent to email server!"
X
LMS 3.3.3.3
EEM Applet (b)

event manager applet LMS_unreachable event track 100 state down action 1.0 reload
75
EEM Script Example Automatic troubleshooting commands

Automatic troubleshooting information is gathered when a port goes down When any port goes down, issue troubleshooting commands in order to gather the required information (TDR tests, interface counters, etc) Store the output of the previous command on a text file in flash memory (or alternatively, send it to an email address)
vent manager policy onportdown.tcl event manager environment _filename flash:onportdown.log
BRKNMS-2000
Cisco Public
76
How about a "self-healing network"? (iii)

How can you assure that your EEM policies are consistent across your network? Know your policies: predefined "show EEM Info" command set in NetShow (RME Tools NetShow) Keep your policies consistent: predefined NetConfig jobs (RME Tools NetConfig) :
EEM Environmental Variables EEM Scripts/Applets
BRKNMS-2000
Cisco Public
77
How about a "self-healing network"? (iv)

Making sure the EEM config is consistent (NetConfig):
BRKNMS-2000
Cisco Public
78
Show commands (i)

Problem definition: 1.When troubleshooting, you get some output from a command, but you are not sure whether that output indicates an exception Solution description: 1.With RME Tools NetShow, run critical show commands periodically, so that you can check back what is the "expected output"
BRKNMS-2000
Cisco Public
79
Show commands (ii)

Some out-of-the-box command sets:
Show IP Routing Info Show Switch VLAN Info Show GOLD Test Results Show EEM Info
If you do not like those, you can define your own Custom Commands! Tip: you can have cisco.com analyze the output! Tip: you can have an external comparison utility (like the freeware ExammDiff) to compare lengthy outputs
80
BRKNMS-2000
Cisco Public
Show commands (iii)

NetShow example:
BRKNMS-2000
Cisco Public
81
Performance Management
BRKNMS-2000
Cisco Public
82
What is Performance Management?

Ensuring that data is properly accessible
Adequate bandwidth Adequate latency Adequate jitter Adequate port capacity
Reducing network "overload" and "inaccessibility" Providing a consistent level of service to the network user Determining utilization trends to proactively isolate and solve performance problems
83
BRKNMS-2000
Cisco Public
IP Service Level Agreement (SLA)

IP SLA probes are used to monitor network performance between any two given points Internetwork Performance Monitor is the LMS component that can configure and monitor these probes
BRKNMS-2000
Cisco Public
84
Network Provider SLA reporting (i)

Problem definition: whenever you report a missed SLA to your network provider, they will not accept your reports as valid, since they include other non-relevant network segments Solution description: run probes involving only the relevant segments
BRKNMS-2000
Cisco Public
85
Network Provider SLA reporting (ii)

How? Internetwork Performance Monitor can help you out:
Extremely easy configuration Tabular / Graphical reports
Tip: UDP probes will give you more accuracy on the measuring of delays (they are timestamped)
BRKNMS-2000
Cisco Public
86
IPM: Collector Configuration
BRKNMS-2000
Cisco Public
87
IPM: Custom Operations Configuration
BRKNMS-2000
Cisco Public
88
Performance-based routing (i)

Problem definition: you have a dual-ISP Internet connection, but your primary ISP will never tear down the connection. Nevertheless, now and then performance will go down Solution description: use IP SLA + Hot-Standby Router Protocol (HSRP) + Enhanced Object Tracking (EOT) at your Internet access routers
BRKNMS-2000
Cisco Public
89
Performance-based routing (ii)

Which target(s) to ping?
Critical Internet Services / Remote VPN endpoints
How to configure it?

IP SLA: use IPM to be able to report on it Enhanced Object Tracking (EOT) + HSRP: IOS CLI IP SLA ID: Admin Index ( Collector Mgmt View) Then you can implement the EOT/HSRP Configuration manually
BRKNMS-2000
Cisco Public
90
HUM: availability reports (i)

Problem definition: I need real quick availability reports for my boss Solution description: do you already know HUM availability default reports?
BRKNMS-2000
Cisco Public
91
HUM: availability reports (ii)

Get out-of-the box availability reports with HUM!
BRKNMS-2000
Cisco Public
92
HUM: availability reports (iii)

What about stacked switches? HUM only reports per-default on L3 instances Easy: report on interface availability. With HUM you do not need to know the Interface IDs, just select the interface groups for the Stack ports
BRKNMS-2000
Cisco Public
93
Optimize your port capacity (i)

Problem definition: It is hard to tell which ports are used and which ports are not used (the server might be down, the user might be in vacation) Solution description: Leverage the UT Switch Reports Additional benefits: More security (unused ports are shutdown)
94
Optimize your port capacity (ii)

Unused Down Access Ports report
BRKNMS-2000
Cisco Public
95
Where to go next?
BRKNMS-2000
Cisco Public
96
NetPro Discussions
User discussions, questions and answers Topic examples:
"Help - Discovery issues with switch stacks" "LWAPP and ciscoworks" "L3 Switch (3560G) Monitoring" "Restore LMS backup from 32 bit to 64 bit OS" And many more!!!
Get quick and uncomplicated expert assistance!

http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network %20Infrastructure&topic=Network%20Management&CommCmd=MB%3Fcmd %3Ddisplay_messages%26mode%3Dnew%26location%3D.ee71a02
97
Cisco Support Wiki

Public Collaboration Platform for Cisco Users Do you like Wikipedia? Let us bring mass collaboration into LMS!! Cisco Support Wiki: thousands of users world wide, more than 22,000 articles. Let us work together!
Cisco Support Wiki home page: http://supportwiki.cisco.com/ Cisco Support Wiki LMS home page: http://supportwiki.cisco.com/ViewWiki/index.php/CiscoWorks_LAN _Management_Solution
98
Key Takeaways
BRKNMS-2000
Cisco Public
99
Abstract
In this breakout session we will discuss how to use some not-sowell-known features of CiscoWorks LAN Management Solution (LMS), to improve the integration with other Management Systems, and to enhance the automation of certain tasks, reducing the manpower required to operate a corporate network. Among the features to be discussed are integration capabilities of Common Services, interaction between LMS components and external tools like TACACS+ Servers, cabling databases or Configuration Management Databases (CMDB), compliance management verifications that can be run with Resource Management Essentials (RME) , or automating tasks using in an orchestrated manner different LMS components with advanced IOS features like Embedded Event Manager (EEM) and IP SLA.
BRKNMS-2000
Cisco Public
100
Using CiscoWorks LMS to its full potential

If you already have it Use it!!! LMS can make your life as a network administrator a lot easier and save time Share your ideas and find new ones on Cisco Technical Forums (NetPro and Cisco Support Wiki)
101
BRKNMS-2000
Cisco Public
BRKNMS-2000
Cisco Public
102
Wrap-Up & Close
Related Sessions
Session ID
BRKNMS-2005 BRKNMS-2007
Title
Video Quality Monitoring and Troubleshooting in Service Provider IP Networks Management Needs of small & medium customers
BRKNMS-2000
Cisco Public
103
Meet The Expert

To make the most of your time at Cisco Networkers 2009, schedule a Face-to-Face Meeting with a top Cisco Expert. Designed to provide a "big picture" perspective as well as "in-depth" technology discussions, these face-to-face meetings will provide fascinating dialogue and a wealth of valuable insights and ideas. Visit the Meeting Centre reception desk located in the Meeting Centre in World of Solutions
BRKNMS-2000
Cisco Public
104
Complete Your Online Session Evaluation

Cisco values your input Give us your feedbackwe read and carefully consider your scores and comments, and incorporate them into the content program year after year Go to the Internet stations located throughout the Convention Center to complete your session evaluations Thank you!
105
BRKNMS-2000
Cisco Public
BRKNMS-2000
Cisco Public
106

BRKNMS 2000

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BRKNMS 2000

Uploaded by

Copyright:

Available Formats

Using CiscoWorks LMS to its full potential

BRKNMS-2000 Jose Moreno (josemor@cisco.com)

2009 Cisco Systems, Inc. All rights reserved.

Using CiscoWorks LMS to its full potential - Agenda

2009 Cisco Systems, Inc. All rights reserved.

2009 Cisco Systems, Inc. All rights reserved.

Introduction Scope Definition

2009 Cisco Systems, Inc. All rights reserved.

2009 Cisco Systems, Inc. All rights reserved.

What this session IS about

What this session is NOT about

Sorry for the TLAs!

The FCAPS model

Integrating LMS into the NMS landscape

2009 Cisco Systems, Inc. All rights reserved.

2009 Cisco Systems, Inc. All rights reserved.

What other tools typically exist out there?

Configuration Management Database (CMDB) Other documentation databases

Integration with CS ACS (i)

2009 Cisco Systems, Inc. All rights reserved.

Integration with CS ACS (ii)

2009 Cisco Systems, Inc. All rights reserved.

Integration with Fault Management Manager-of-Managers (MoM)

2009 Cisco Systems, Inc. All rights reserved.

CiscoWorks Integration Utility

Fault management architecture with DFM

Cisco Info Center Problem with A

High temperature Not reachable

2009 Cisco Systems, Inc. All rights reserved.

Send traps out of syslog messages (i)

No info about the event!

2009 Cisco Systems, Inc. All rights reserved.

Send traps out of syslog messages (ii)

2009 Cisco Systems, Inc. All rights reserved.

Send traps out of syslog messages (iii)

2009 Cisco Systems, Inc. All rights reserved.

Send traps out of syslog messages (iv)

2009 Cisco Systems, Inc. All rights reserved.

Other CiscoWorks tools (i)

2009 Cisco Systems, Inc. All rights reserved.

Other CiscoWorks tools (ii)

2009 Cisco Systems, Inc. All rights reserved.

Integration with CMDB (i)

2009 Cisco Systems, Inc. All rights reserved.

Integration with CMDB (ii)

2009 Cisco Systems, Inc. All rights reserved.

Integration with CMDB (iii)

2009 Cisco Systems, Inc. All rights reserved.

Integration with CMDB (iv)

2009 Cisco Systems, Inc. All rights reserved.

Integration with CMDB (v)

XML Payload for device inventory export (exportinventory_DIST1.xml)

2009 Cisco Systems, Inc. All rights reserved.

Integration with CMDB (vi)

Integration with generic databases (i)

2009 Cisco Systems, Inc. All rights reserved.

Integration with generic databases (ii)

2009 Cisco Systems, Inc. All rights reserved.

Integration with generic databases (iii)

2009 Cisco Systems, Inc. All rights reserved.

Integration with generic databases (iii)

2009 Cisco Systems, Inc. All rights reserved.

Integration with generic databases (iii)