- Is the Cisco MARS mission going to abort?
- First iPhone worm spreads Rick Astley wallpaper
- 10 stunning 3D buildings made with Google SketchUp
- Open source software ready for big business
- Four reasons to buy (and one reason to avoid) the Droid
I’d like to first say hello to everyone reading our new network management columns. This is a first for me and I welcome feedback and commentary from anyone and everyone in response to my musings here. I hope to hit on key topics that are regularly discussed in our business and provide a broader discussion of those topics for more public consumption. We hope to have these columns coming your way on a weekly basis from here on out.
To start off I’d like to pick things up from where my colleague, Dennis Drogseth, left off with his last column, talking about trends in the network management landscape. Only this week, I’d like to further explore how network management no longer lives in a corporate vacuum and has to cohabitate with a myriad of other organizational groups and departments - departments the network team never before had to contend with or consult with in the course of accomplishing its daily duties.
In the golden days of network management, let’s say pre-2000, the network team handled everything and anything that touched the network backbone of the organization. Whether it was tracked in the form of packets, sessions, transactions, protocols, or by ports it was the sole purview of the network team. Of course there was a prevailing attitude that if anything went wrong or didn’t work on the corporate IT front, then it was the network’s fault. It didn’t matter whether it was a server-side issue or an errant application. It was always the network’s fault.
Assuming the source of the problem was really focused in the server or application areas, members from those portions of the organization would have to get any network-related information directly from the network team via formal request. They would typically submit their request, the network team would review their request, and if their request was deemed worthy, the information was sent over to the requesting team in its most raw or basic form. The recipients would just have to deal with what they were provided and use that information to try and isolate the source of the problem, identify the most appropriate corrective course of action, and then institute a fix, all with minimal information to go on.
Now, let’s fast-forward to the present day. Requests for data, support, cooperation, etc., from the network team aren’t just coming from their traditional IT counterparts - they're originating from across the entire enterprise. Those requests are coming from groups and departments like quality, procurement, legal, test, audit, compliance, senior management, database, the data center, and within the NOC itself. Imagine the network team trying to field requests from all those diverse groups back in the golden days of network supremacy. They would have been doing nothing but responding to all those requests all day long.
Partner Content
Blue Stripe Software
www.bluestripe.com/
Improving Application Performance Troubleshooting
Diagnosing why an application is slow is hard, at times taking days or weeks to isolate and resolve. This paper explains the challenges involved using current management tools, provides a 'wish list' for application management and analysis, and explains the need for an application system-wide approach that monitors entire applications, not components.
Download Whitepaper
Virtual Vigilance: Managing Application Performance in Virtual Environments
This paper highlights the impact of virtualization on application performance. "Managing Application Performance in Virtual Environments" states: "Best-in-Class organizations are predominately taking actions around improving visibility across both physical and virtual systems, assessing the business impact of application performance and understanding interdependencies of applications in virtualized environments."
Download Whitepaper
Application Service Requests: The Missing Link for Pragmatic ITSM
Forrester Research analyst Glenn O'Donnell and BlueStripe co-founder Vic Nyman discuss a breakthrough approach to application problem management. Learn the new approach for ITSM problem management, which provides: Rapid isolation of application slow-downs to specific components for quick problem resolution, 24/7 monitoring for proactive notification of potential issues before end users are impacted and much more.
Register for Webcast
Comment