Home > Data Center Management Tips > Data Center Operations and Design Tips > Root cause analysis tips for optimal network management
Data Center Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

DATA CENTER OPERATIONS AND DESIGN TIPS

Root cause analysis tips for optimal network management


Rajesh Awasthi
10.08.2009
Rating: --- (out of 5)


Enterprise IT tips and expert advice
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


Rajesh Awasthi, root cause analysis spokesperson, EMC Ionix
Rajesh Awasthi
Root cause analysis (RCA) has been around as a technology for some time, but it is gaining popularity of late thanks to an increase in the number of managed devices in data centers. Imagine a data center where 20,000 switch ports generate events and warnings every minute. In such cases, it is almost impossible to identify the problem. RCA comes in as an ally in such situations.

In order to deliver high levels of IT infrastructure availability, organizations need tools that help them isolate these problems. For example, the mean time required to isolate a problem takes up 65% of an administrator's time. RCA helps reduce this.

It's common to find that multiple events and alarms are generated during a device failure -- not just from malfunctioning network devices but also from adjacent attached devices. For example, if a switch generates an alarm that a particular port and card have gone down, then the servers attached to that switch also generate an alarm. This is where RCA and event correlation accurately identify the problem.

RCA is very useful for management of SLAs between the IT team and business users. RCA ensures higher levels of IT infrastructure availability.

To carry out a successful RCA exercise, it is wise to follow certain steps. The first step is to perform detailed mapping. This should be supplemented by selection of the right management tool.

Mapping: In order to conduct effective RCA, you must identify what your organization wants to manage. You can achieve this by creating a managed object definition language (MODL) model.

The next step is to create a topology of the data center to be managed, which encompasses all the managed elements. These may include routers, switches, servers and storage equipment, or particular applications that run on this infrastructure. Thus, a map is created of the data center and infrastructure network along with correlation.

To explain this mapping, let's take the example of a core router in the centralized data center. Typically, multiple access routers connect to this core router. So this connectivity between the network's core routers and access routers will be shown in the mapping model. These router-based networks will be connected to switching devices at each of the locations. There will be different servers installed on the switches and different applications installed on these servers. Thus, a map of this information is created, which is known as the topology.

While RCA can achieve many wonderful things, it also introduces overhead issues into a network. Network overheads are created during discovery of the network elements that have to be managed.
Select the right network management tool: Always ensure that your selected network management tool can auto-discover the topology or deployment scenario within your organization. It should be dynamic enough to cope with the attendant changes.

Data centers are now in a constant state of flux, since infrastructure continually changes to meet business needs. The topology itself should be able to effectively discover all infrastructure elements the first time. The tool should keep this topology updated on a periodic basis (or as and when required) so that it is the exact replica of what has been deployed in the data center.

Post the network management tool rollout: While RCA can achieve many wonderful things, it also introduces overhead issues into a network. Network overheads are created during discovery of the network elements that have to be managed. To counter this situation, it's essential that you schedule the discovery timing. Thus, you do not overload the network with queries related to discovery tools. A boundary may also be created, so that only a certain area needs to be discovered. That is one way of reducing the discovery time.

About the author: The director of sales for Ionix in India, Rajesh Awasthi is responsible for EMC's Ionix software business in India and the SAARC region. He has worked on sales, business development, consulting, partnership management, alliance management and product management for telecom software, data network, IT infrastructure, disaster recovery and business continuity solutions. Awasthi has worked on quality process building and implementation for increasing efficiency and has also won several awards.

(As told to Jasmine Desai.)

Rate this Tip
To rate tips, you must be a member of SearchDataCenter.IN.
Register now to start rating these tips. Log in if you are already a member.




BROWSE BY TAG
Data center operations and asset management,   Data center systems and application management,   Data Center Operations and Design Tips,   VIEW ALL TAGS

Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google



RELATED CONTENT
Data center systems and application management
Mixed virtual environments catching on
iSCSI SANs in a virtual server environment: Five best practices
Finding the best capacity planning tool for your data center
Syntel's disaster recovery formula for customer-centric operations
Comparing risks of cloud and virtualization to your data center apps
RAID 6: A comparison with RAID 5
Windows Server Backup: Key feature in Windows Server 2008 R2
Data center migration tips for SMBs
Server virtualization eliminates pain-points at Apeejay Surrendra
'Avatar' post-production combines BlueArc and NetApp clustered NAS

Data Center Operations and Design Tips
Data center power and cooling revamp success story at CRIS
Disaster recovery checklist: What you need in your DR budget
Data center power and cooling strategies that insure IFFCO TOKIO
Disaster recovery boosts customer service ops at Punjab National Bank
Using information lifecycle management for mainframe disaster recovery
Disaster recovery streamlines business at Jindal Steel
Finding the best capacity planning tool for your data center
Syntel's disaster recovery formula for customer-centric operations
Business impact and risk assessments in IT disaster recovery planning
Data center migration tips for SMBs

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary

DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

HomeNewsTopicsITKnowledge ExchangeTipsMultimediaWhite Papers
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2009 - 2010, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts