20 posts categorized "Back-to-Basics" Feed

LMTV LIVE | How To Diffuse The IT Blame Game (with Keith Bromley and Scott Peerbolte)

 

 

LIVE EVENT START TIME : 9:30 AM PST, Wednesday, June 27th, 2018

6a00e008d95770883401b8d2e041f0970c-800wiThis week we will be talking with Keith Bromley (from Keysight Technologies, formerly Ixia) and Scott Peerbolte (of Corvil) about how you can help break down silos and reduce the blame game that are common for most IT departments. 

For instance, how well do your IT departments communicate with each other?  

Enterprises typically contain four or more IT sub-departments (Security, Network Operations, Virtual DC, Capacity Planning, Service Desk, Compliance, etc.) and it’s quite common for them to be at odds with each other, even in good times. For instance, there’s often contention over capital budgets, sharing resources, and headcount. But let’s be generous. Let’s say that in normal operations things are usually good between departments. What happens if there’s a breach though, even a minor one? Then things can change quickly. Especially if there are problems with acquiring accurate monitoring data for security and troubleshooting areas. Finger pointing can quickly result. 

So, what can you do? One answer is to create complete network visibility (at a moment’s notice) for network security and network monitoring/troubleshooting activities. Join us on this podcast to learn how.

Some key thoughts we will discuss during the event:

 

Continue reading "LMTV LIVE | How To Diffuse The IT Blame Game (with Keith Bromley and Scott Peerbolte)" »


Fixing Mailto Problems On Windows 8 (by Tony Fortunato)

I appreciate all the positive feedback I’ve been receiving from my PC articles since I typically post about networking and Wireshark topics.

In this video I discuss how to fix a mailto problem I ran into while setting up a network management computer for a client.

The mailto: URL can be used by webpages or applications to send emails. In the video I used a Chrome extension as a test to illustrate the issue and fix.

 

 

Continue reading other LoveMyTool posts by Tony Fortunato »


LMTV LIVE | How to Create Scalable Visibility in your Data Center (with Chris Bihary of Garland Technology)



YouTube LIVE event start time: Wednesday, July 19, 2017, 9:30 AM PST


Garland170x200How do you scale your network infrastructure to support multiple monitoring tools - while ensuring 100% packet capture?

This is the problem we have been hearing in the last few years. Data centers (D1 & D2) and enterprise networks have many challenges and two of the big ones are providing the IT department anytime access to full-duplex traffic, while guaranteeing full packet capture. Now layer on top of that a stack of 1G legacy monitoring tools in addition to the migration to 10G/40G and 100G speeds.

Join us for to learn about the latest visibility solution from Garland Technology’s as they introduce and demonstrate their Passive Fiber Modular Chassis System, a flexible, scalable and affordable high density solution for managing up to 24 links in a 1U box at network speeds of 1G/10G/40G/100G.


Click to read other LMTV posts by contributors of LoveMyTool »


Network Troubleshooting Tip - Understand the System (by Paul Offord)

When we get to the point in an investigation where we are about to break out Wireshark, the complexity of the packet analysis can seem quite daunting. And yet by covering a few key points can dramatically cut the time needed to analyze any diagnostic data.

In my previous post I covered the selection of a single symptom for investigation. In this blog we'll discover the need to understand more than just the network connectivity.

I remember visiting a third party data center and chatting to a network engineer who had been leading the investigation into a Citrix performance problem. He had spent months looking at this issue and I was shocked to discover how little he understood about the system he was analyzing. I asked him to draw a rough diagram showing the main components of the system and how they talked to each other. He couldn't and didn't see the need. As far as he was concerned, packets went into one switch port and they came out of another. "I don't need to know what connected to those ports", he informed me.

This may be an extreme example, but I have attended many meetings with teams that have been investigating a performance problem and nobody is able to draw the system on a whiteboard.

Ipt_diag

Modern systems are very complex, and so we need to sketch out the system with enough detail to provide everyone with an understanding of how it works, but not so much that it's overwhelming.  Advance7 has found ...

Continue reading "Network Troubleshooting Tip - Understand the System (by Paul Offord)" »


Network Troubleshooting Tip - Focus on a Single Symptom (by Paul Offord)

When we get to the point in an investigation where we are about to break out Wireshark, the complexity of the packet analysis can seem quite daunting. And yet by covering a few key points can dramatically cut the time needed to analyze any diagnostic data.

In my previous post I covered the need to thoroughly understand a symptom. In this blog we'll look at the dangers looking for a common cause for multiple symptoms.

Imagine you are faced with a situation where users are complaining about three issues:

  • Word documents should open in less than 5 seconds, but intermittently take more than 30 seconds.
  • Excel workbooks should save in less than 15 seconds, but intermittently take more than 60 seconds.
  • Opening an Outlook Inbox should take less than 20 seconds, but sometimes takes more than 3 minutes.

All problems are reported as having started at the same time, and there’s a widespread belief that they are being caused by a network issue. This is the point where alarm bells should start to ring.

  Symptoms1

 

Maybe some of the symptoms are down to the same root cause, but maybe they are not, and starting by assuming they are is likely to lead to a very frustrating time. The choice of a single symptom and ...

Continue reading "Network Troubleshooting Tip - Focus on a Single Symptom (by Paul Offord)" »