In previous articles we reviewed the overall topic of management interfaces to Taps and NPBs and in subsequent chapters took a deep dive into the topics of Fault Management and Configuration Management. In this chapter we will focus on Software Management and its related topics. Subsequent chapters will cover other management topics including accounting, performance monitoring, security and remote access.
Security scanning of critical devices should be standard practice on networks, but what about other devices such as TAPs, Network Packet Brokers (NPB) and Bypass switches?
This article is the second in a multi-part series on the management of Taps and Network Packet Brokers. This chapter focuses on Fault Management including Detection, Correlation/Aggregation, Diagnosis/Isolation, Restoration, and Resolution.
When looking at some of the simpler network device types such as taps and network packet brokers there are a few factors involved in trying to determine which management system interfaces should be supported and to what extent.
Network Taps are a crucial part of the tool kit used by engineers responsible for network security, performance, and capacity management. Taps are robust devices that rarely ever exhibit issues, but as with any network equipment – it may occasionally be necessary to troubleshoot them. In some cases this is an inherent part of a multi-layered process of elimination, but in certain circumstances the process might begin with the Tap itself. The following procedures are presented with Datacom Systems fiber Taps* in mind, but the general principles are applicable to all brands of Taps.
In my previous articles we reviewed the overall topic of management interfaces to Taps and NPBs and took a deeper dive into Fault Management. In this chapter we will focus on the areas of configuration and provisioning management topics. Subsequent chapters will cover other management topics including software management, accounting, performance monitoring, security and remote access.