I would look at uptime and availability, CPU & memory utilization, possible hack attempts on the firewall, IDS signatures, and bandwidth utilization yada yada yada.
There are so many things COULD monitor but that does nt mean you SHOULD monitor. What you really need to do is sit down with all the decision makers and come up with what is critical at your organization. One company may keep a close watch on the WAN bandwidth and another company may want to pay closer attention to the firewall or router availability. Once you have that information you will be better prepared to make a list of what you need to be able to monitor and manage from a central location.
This tool is not a full blow suite like Concord e-health but has great support and templates are constantly being developed for it. I use it mostly to monitor network bandwidth on routers and switches sometime processor utilization and lately I've been using it to montior the classes for my different QOS queues..
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...