Grant Ho, SVP, NetBrain Technologies

Author Archives: Grant Ho, SVP, NetBrain Technologies

Why dynamic mapping is changing network troubleshooting for the better

Effective network troubleshooting requires experience and a detailed understanding of a network’s design. And while many great network engineers possess both qualities, they still face the daunting challenge of manual data collection and analysis.

The storage and backup industries have long been automated, yet, for the most part, automation has alluded the network, forcing engineering teams to troubleshoot and map networks manually. Estimates from a NetBrain poll indicate that network engineers spend 80% of their troubleshooting time collecting data and only 20% analyzing it. With the cost of downtime only getting more expensive, an opportunity to significantly reduce the time spent collecting data is critical.

To read this article in full or to leave a comment, please click here

Why dynamic mapping is changing network troubleshooting for the better

Effective network troubleshooting requires experience and a detailed understanding of a network’s design. And while many great network engineers possess both qualities, they still face the daunting challenge of manual data collection and analysis.The storage and backup industries have long been automated, yet, for the most part, automation has alluded the network, forcing engineering teams to troubleshoot and map networks manually. Estimates from a NetBrain poll indicate that network engineers spend 80% of their troubleshooting time collecting data and only 20% analyzing it. With the cost of downtime only getting more expensive, an opportunity to significantly reduce the time spent collecting data is critical.To read this article in full or to leave a comment, please click here

Why dynamic mapping is changing network troubleshooting for the better

Effective network troubleshooting requires experience and a detailed understanding of a network’s design. And while many great network engineers possess both qualities, they still face the daunting challenge of manual data collection and analysis.The storage and backup industries have long been automated, yet, for the most part, automation has alluded the network, forcing engineering teams to troubleshoot and map networks manually. Estimates from a NetBrain poll indicate that network engineers spend 80% of their troubleshooting time collecting data and only 20% analyzing it. With the cost of downtime only getting more expensive, an opportunity to significantly reduce the time spent collecting data is critical.To read this article in full or to leave a comment, please click here

Why dynamic mapping is changing network troubleshooting for the better

Effective network troubleshooting requires experience and a detailed understanding of a network’s design. And while many great network engineers possess both qualities, they still face the daunting challenge of manual data collection and analysis.

The storage and backup industries have long been automated, yet, for the most part, automation has alluded the network, forcing engineering teams to troubleshoot and map networks manually. Estimates from a NetBrain poll indicate that network engineers spend 80% of their troubleshooting time collecting data and only 20% analyzing it. With the cost of downtime only getting more expensive, an opportunity to significantly reduce the time spent collecting data is critical.

To read this article in full or to leave a comment, please click here

Why dynamic mapping is changing network troubleshooting for the better

Effective network troubleshooting requires experience and a detailed understanding of a network’s design. And while many great network engineers possess both qualities, they still face the daunting challenge of manual data collection and analysis.

The storage and backup industries have long been automated, yet, for the most part, automation has alluded the network, forcing engineering teams to troubleshoot and map networks manually. Estimates from a NetBrain poll indicate that network engineers spend 80% of their troubleshooting time collecting data and only 20% analyzing it. With the cost of downtime only getting more expensive, an opportunity to significantly reduce the time spent collecting data is critical.

To read this article in full, please click here