We recently updated our
Terms and Conditions for TechRepublic Premium.
By clicking continue, you agree to these updated terms.
Invalid email/username and password combination supplied.
An email has been sent to you with instructions on how to reset your password.
Welcome to TechRepublic!
All fields are required. Username must be unique. Password must be a minimum of 6 characters and have any 3 of the 4 items: a number (0 through 9), a special character (such as !, $, #, %), an uppercase character (A through Z) or a lowercase (a through z) character (no spaces).
Due to scheduled maintenance, the ability to log in to your account and make purchases will be disabled December 1 - 2.
If you’re talking about really monitoring/troubleshooting at the physical layer, then you either need a T1 CSU/DSU that has built-in monitoring capabilities, or deploy a T1 Tap to allow monitoring to happen in another device. There’s a ton of capability built into the Cisco gear, of course.
In terms of true low-level analysis, using a T1 Tap and a Fluke Optiview box or a Network Instruments Observer box…those will tell you everything, period.
Instead of using some expensive T1 analyzer you could just monitor the traffic that comes out of the CISCO box. This way you are actually looking at what is coming and going from your network. Simple statistics can be gleaned from any IDS\IPS solution but if you want deep packet inspection I would recommend running an in-line wireshark.
The practical issue is that if you are looking at issues at layer 3, and it’s a layer 1 problem, you then have to get to the layer 1 level, and if you don’t have that capability in place, then it takes valuable time to set that up.
The Cisco NAM (network analysis module) is essentially the same thing as a WireShark box on a card, except that you don’t need to run cables, since the NAM is connected to the backplane of the switch or router, and you just mirror a port to it.