nms monitoring different network applications on a single or mul
When we talk about managing devices using a Network Management Tool or Application, the most simple management fundamental is the devices should be reachable to the NMS Server.
No matter how the network topology is made and what protocols are in order, devices needs to communicate with the NMS server freely. Due to this I am not sure if any NMS will be able to show you devices with such topologies automatically, but you have to make such logical groupings, be it as per your device zones, device platforms, technolgies (wifi, Voice etc), VRF's and other functional distributions.
You can manually group such logical separations on your NMS tool to match your network.
**Rating Encourages contributors, and its really free. **
[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...